String encoding problem (WSMethodInvocation)

[Nick Toumpelis]

I assumed that something like this might be the problem, so I overode  
the serialization procedure with  
WSMethodInvocationAddSerializationOverride. And it works (more or less).

It appears that there is an additional bug with the actual encoding  
itself.

Nick

On 25 Ιαν 2008, at 10:06 ΠΜ, Stéphane Corthésy wrote:

> rdar://problems/4792516
>
> Sent on 19-Oct-2006
>
> WebServicesCore: SOAP messages miss charset information in HTTP header
>
> Summary:
> HTTP header in HTTP requests generated by WebServicesCore, for  
> kWSSOAPBodyEncodingStyle, miss  a 'charset=utf-8' key-value in the  
> content-type header.
>
> Steps to Reproduce:
> 1) Using WebServicesCore, create a web invocation, with debug  
> information on.
> 2) Send the invocation, and wait for result.
> 3) When receiving results, look at the outgoing headers, in the  
> result dictionary.
>
> Expected Results:
> The header value for 'content-type' should contain the charset used  
> to encode the body, because body is encoded in UTF-8, and without  
> any information in the header, all receivers will decode body using  
> ISOLatin1 charset.
>
> Actual Results:
> If sent body contains non-ASCII characters, body is wrongly decoded  
> using ISOLatin1.
>
>
> Apple never replied to that bug report. Status is still set to open,  
> though it's 15 months old.

Nick Toumpelis :: Software Developer :: BEng (Wales), MSc (Manchester)
Thessaloniki, Greece :: email:nick at toumpelis.me.uk :: AIM:nick at toumpelis.me.uk