-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation cannot be found issue #873
Comments
Looks good. A pull request would be most appreciated. Feel like submitting one? |
Ok. I will submit PR as soon as possible. |
kristijanmihaljinac
added a commit
to kristijanmihaljinac/SoapCore
that referenced
this issue
May 11, 2022
Update SoapEndpointMiddleware.cs - TryGetOperation method
andersjonsson
added a commit
that referenced
this issue
May 11, 2022
#873 Operation cannot be found issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi to all,
We have a problem if the header soapaction is not specified. When soapaction is not specified then middlware cannot find which service method to call.
Method name:
![image](https://user-images.githubusercontent.com/59372416/167352050-40ffabc0-33eb-4f2a-bd03-2915ab40c652.png)
I found a solution so I ask if you could add that to the code.
Problem is in TryGetOperation method. The picture shows the as is state and that is the state with the change. After the change, there is no problem anymore. My question is if you could add that in the next version.
The text was updated successfully, but these errors were encountered: