🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: microsoft.public.xml.soap
Article #3

Re: Character encoding in SOAP-message

#3
From: berryv
Date: Wed, 04 Apr 2007 11:13
29 lines
2718 bytes
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
Technical Details
Message-ID: <1175685227.545085.53250@y66g2000hsf.googlegroups.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!postnews.google.com!y66g2000hsf.googlegroups.com!not-for-mail
References: <1175501188.146830.74710@p77g2000hsh.googlegroups.com> <Op$Uw$bdHHA.3648@TK2MSFTNGP05.phx.gbl>

Show Full Headers
Complete Article Headers
X-Google-Thread: 10aac8,2d705d9391d4c101
X-Google-Thread: 114096,2d705d9391d4c101
X-Google-Attributes: gid10aac8,gid114096,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!postnews.google.com!y66g2000hsf.googlegroups.com!not-for-mail
From: berryv@gmail.com
Newsgroups: microsoft.public.xml.soap,borland.public.delphi.webservices.soap
Subject: Re: Character encoding in SOAP-message
Date: 4 Apr 2007 04:13:47 -0700
Organization: http://groups.google.com
Lines: 30
Message-ID: <1175685227.545085.53250@y66g2000hsf.googlegroups.com>
References: <1175501188.146830.74710@p77g2000hsh.googlegroups.com>
   <Op$Uw$bdHHA.3648@TK2MSFTNGP05.phx.gbl>
NNTP-Posting-Host: 62.177.228.218
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1175685232 24204 127.0.0.1 (4 Apr 2007 11:13:52 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 4 Apr 2007 11:13:52 +0000 (UTC)
In-Reply-To: <Op$Uw$bdHHA.3648@TK2MSFTNGP05.phx.gbl>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3,gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 ROVDC01
Complaints-To: groups-abuse@google.com
Injection-Info: y66g2000hsf.googlegroups.com; posting-host=62.177.228.218;
   posting-account=n7UcZAwAAADZHiilI6sOw3Rm2FzYG0cY