[Mono-dev] Bug in System.Web.Services inSoapMessage.ContentEncoding

[Vladimir Krasnov]

Hello,

You right, Lluis
I've fixed this in different way. Please look at attached files.

Vladimir Krasnov

-----Original Message-----
From: Lluis Sanchez [mailto:lluis at ximian.com] 
Sent: Tuesday, March 14, 2006 1:51 AM
To: Vladimir Krasnov
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] Bug in System.Web.Services inSoapMessage.ContentEncoding

This patch is not correct. You can't add a protected property that's
doesn't exist in the MS api. Moreover, I don't think this is the right
way of updating the request. Why not set the initial content type to the
message, process it, and then update the request from the resulting
message?

El lun, 13-03-2006 a las 09:18 -0800, Vladimir Krasnov escribió:
> Hello,
> 
> ContentEncoding property has a wrong value in a soap message that passed
> to ProcessMessage method. Look attached sample that reproduces the
> problem. 
> 
> Please approve the attached patches that fix this problem.
> I will commit if no one objects.
> 
> Vladimir Krasnov
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

-------------- next part --------------
A non-text attachment was scrubbed...
Name: HttpSoapWebServiceHandler.cs.1a.patch
Type: application/octet-stream
Size: 940 bytes
Desc: HttpSoapWebServiceHandler.cs.1a.patch
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060314/820c1582/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SoapServerMessage.cs.1a.patch
Type: application/octet-stream
Size: 722 bytes
Desc: SoapServerMessage.cs.1a.patch
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060314/820c1582/attachment-0001.obj