🚀 go-pugleaf

I'm not sure as I don't know much about Delphi or your web server.
If it ignores the request header for the encoding then it must be working it 
out from the actual file, reading the first few characters and deciding.
Does that mean it's working now or do you still have a problem?

-- 

Joe Fawcett (MVP - XML)
http://joe.fawcett.name

<berryv@gmail.com> wrote in message 
news:1175685227.545085.53250@y66g2000hsf.googlegroups.com...
> On Apr 3, 9:16 am, "Joe Fawcett" <joefawc...@newsgroup.nospam> wrote:
>> Errors like that normally mean that the encoding declared in the XML,
>> 'ISO-8859-1', in this case is not the actual encoding used. How do you
>> specify the encoding in your service. I would suggest changing the
>> decalration to UTF-16 or UTF-8 anyway, why restrict yourselves?
>>
>
> Thank you for answering.
>
> I've used a sniffer to see what actually goes over the line. I've uses
> different clients to test it. Using Perl I managed to reproduce the
> problem.
> When I use Perl (Soap::Lite) I can set the encoding. When I set the
> encoding to ISO-8859-1 the client generates an http request with in
> it's request-header this ISO encoding. The acual message (the soap-
> envelope) uses ISO-encoding (I can see the codes using the sniffer).
> This client generates no error. When I set the encoding to utf-8 the
> http header states utf-8. The actual message, though, is encoded in
> ISO. This version gives the soap-error.
>
> When I use a javascript-client, I can set the http-header to ISO and
> to utf-8. Both versions, however, code their content in uft-8!?!
> Neither one of these clients gives an error. It seems that the
> receiving soap-server knows which encoding is used, but it doesn't
> look at the request-header. How can the server tell which encoding is
> used?
>
> Thanks.
> Berry
>