Bug 1244 - Soap12 message serialisation incorrect for ReplyTo header value (EndpointAddress10)
Summary: Soap12 message serialisation incorrect for ReplyTo header value (EndpointAddr...
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 4.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Reported: 2011-10-05 00:15 UTC by Justin S.
Modified: 2011-10-06 02:20 UTC (History)
3 users (show)

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

Proposed fix (1.08 KB, application/octet-stream)
2011-10-05 10:05 UTC, Rolf Bjarne Kvinge [MSFT]

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 on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Justin S. 2011-10-05 00:15:59 UTC
Creating a CustomBinding with a TextMessageEncoding for Soap12, with Addressing10 results in a malformed Soap12 envelope.

The ReplyTo header is serialised incorrectly:



It appears that the EndpointAddress10 is being serialised incorrectly.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2011-10-05 08:38:51 UTC
I can reproduce this (using the test case in your support request), looking at it now.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2011-10-05 10:05:08 UTC
Created attachment 596 [details]
Proposed fix
Comment 3 Rolf Bjarne Kvinge [MSFT] 2011-10-05 10:06:01 UTC
Atsushi, does the proposed fix look correct to you?
Comment 4 Atsushi Eno 2011-10-05 10:12:31 UTC
Yes, looks like it's doing the same as non-2.1 code as long as applicable.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2011-10-06 02:20:22 UTC
Yes, that's exactly what it's doing.

Fix committed, I think it will reach MonoTouch 5 (due to come out very soon).