-
Notifications
You must be signed in to change notification settings - Fork 565
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
Not able to consume a WCF service with CustomBinding endpoint with messageversion as Soap12 #2711
Comments
I have the same problem(also consuming from net core 2. Soap11 works Soap12 throws this exception. In fact I can't even see the request going out in fiddler |
Hi, My .net solution was implemented to use custom binding on Soap11WSAddressing10, when moving to .Net core Soap11WSAddressing10 was not available option and Soap12WSAddressing10 is not working :( |
I did some investigation and I can understand why Soap11WSAddressing10 doesn't work. The code for Soap11 here is missing on core. The issue with just Soap12 I'm not able to see what the issue is after a few minutes of digging through the code and I'll need to do more investigation. |
@mconnew Need open test issue for write tests for Soap11WSAddressing10 and Soap12, include details needed. |
@StephenBonikowsky Can we have test for this? |
Hello, |
@swiftarrow101 This hasn't been fixed yet, however, it is in our pipe to work on. |
Soap12 without Addressing lost the action attribute in the ContentType header. The quicker solution is move lines from wcf/src/System.Private.ServiceModel/src/System/ServiceModel/Channels/HttpChannelFactory.cs Lines 1178 to 1182 in 1e49a79
to |
Is there a workaround for this issue until it's fixed in a future release? |
I think I came up with a workaround. After looking through the source I saw that if I try to add a "SOAPAction" header, it will be added as a Content-Type header parameter. This seems to work:
I have to wrap every method call with it, so this:
becomes:
edit:
|
Updated namespace for SOAP 1.2 to fix #181 I had to wrote it this way, because .NET Core currently doesn't have 'Soap12' MessageVersion member. When it will be present (see dotnet/wcf#2711) implementation should be updated to cover new member.
I have to consumer a WCF service from my Core2.0 API. The WCF service has custombiding with messageVersion as Soap12.
Please find the wcf service binding configuration.
I am using System.ServiceModel.Primitives to create the CustomBinding from my .NET Core Code.
Please find the code below
I am getting the below error from this call.
This will work for any other message version like Soap11, Soap12WSAddressing10 which is directly present in MessageVersion class. It is not working when i am creating messageversion using CreateVersion method as there is no in-built support for Soap12 as it used to be with the framewrok dll
The text was updated successfully, but these errors were encountered: