Bug 34264 - Soap version mismatch
Summary: Soap version mismatch
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web.Services ()
Version: 4.0.0
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-09-24 23:11 UTC by abhi512
Modified: 2015-09-24 23:11 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 34264 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description abhi512 2015-09-24 23:11:53 UTC
The web services ( obsolete .asmx files) deployed on mono runtime 4.0  is hosted on xsp4 web server.
The services has not been able to communicate to client which is sending soap request based on soap 1.2 version.

When tested the soap version is 'default' and when I try to remove soap version 1.1 from the web.config file, it throws an error ( "Internal server error") when I add soap version 1.2, it tries to send response to client in soap 1.2 format, which results in error at client side.

To summarise this, I have not been able to disable soap 1.1 and I can't use it as well.