[Mono-bugs] [Bug 82610][Min] Changed - The Content-Type values must be matched case insensitive in SoapHttpClientProtocol

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Aug 29 04:14:53 EDT 2007

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by christian.schilling at mac.com.


--- shadow/82610	2007-08-28 06:53:18.000000000 -0400
+++ shadow/82610.tmp.28848	2007-08-29 04:14:53.000000000 -0400
@@ -67,6 +67,14 @@
 ------- Additional Comments From atsushi at ximian.com  2007-08-28 06:53 -------
 I very much agree with you that mono should be compliant with HTTP
 RFC. However there are couple of ".NET compatibility always rules"
 people who assert that .NET compares HTTP methods in case insensitive
 manner. So I wonder if this issue could be fixed (by not technical mean).
+------- Additional Comments From christian.schilling at mac.com  2007-08-29 04:14 -------
+I am not quite sure, if I understand your comment. What is the
+relationship between a case-insensitive web/http method call and the
+current case-sensitive evaluation of the Content-Type? I just wanted
+to say that the type and subtype of the Content-Type should be
+evaluated case-INsensitive (e.g. text/xml (the only recognized
+version), TEXT/XML and Text/Xml should be the same).

More information about the mono-bugs mailing list