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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=74878 --- shadow/74878 2005-12-02 21:56:46.000000000 -0500 +++ shadow/74878.tmp.32185 2005-12-03 10:09:19.000000000 -0500 @@ -202,6 +202,15 @@ > There is still an issue with async calls and the patch, > probably because the mono formatter's ProcessMessage > doesn't deal with ServerProcessing.Async. Wrong guess. The Content-Type is missing from async requests ;-) + +------- Additional Comments From [EMAIL PROTECTED] 2005-12-03 10:09 ------- +.NET (1.0, 1.1, 2.0) relies on the Content-Type: + +If the request doesn't contain the content-type header *and* +there are more then one formatter in the chain *and* +the request is not suitable for the first formatter in the +chain, .NET throws a serialization exception. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
