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

[Lluis Sanchez]

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