Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.uk;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=2AQ+KWPVtlT7lEACqgIgt05vfxF8JCNx4jelWIoNTFMYfqD/0oWEqSqHcgJP/kikC/r2Ztu3ENTmk6iNPScIcOjU9nO12jsbbCk+YEGegWA9aH+jEARJgktqpU6YJeYDFrr8+glSdwTlEuzGHxRUG0Hw5Zc51ILZ2DuHV6f0RYE=;
Date: Thu, 23 Oct 2008 09:36:47 +0000 (GMT)
From: Mike Kyle <m_t_k_nospam@yahoo.co.uk>
Subject: UTF8 problem?
To: httpclient-users@hc.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-912371670-1224754607=:6161"
Message-ID: <74432.6161.qm@web24005.mail.ird.yahoo.com>

--0-912371670-1224754607=:6161
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I set an EntityEnclosingMethod request entity to be a ByteArrayRequestEntit=
y. This entity has the Java characters "\u4E2D\u6587" as the corresponding =
UTF8 bytes (UTF8 =3D 0xE4,0xB8,0xAD,0xE6,0x96,0x87). This is confirmed by l=
ogging httpclient.wire.content. There I see the UTF8 values.=0A=0AHowever w=
hat appears to really get transmitted is the corresponding Java characters =
rather than the UTF8 values! As this is supposedly a UTF8 encoded XML docum=
ent the receiver is not best pleased. This is confirmed by performing HTTP =
sniffing using org.apache.axis.utils.tcpmon.My suspicion is that somehow a =
character handler is intervening? =0A=0ADebugging HttpConnection implied th=
at the output stream is a BufferedOutputStream wrapping a java.net.SocketOu=
tputStream. I had assumed that the socket streams would be byte oriented. T=
he content type is set to 'text/xml; chartset=3D"utf-8"'.=0A=0AI am normall=
y using HttpClient 3.0 + but the latest 3.1 appeared to react exactly the s=
ame.=0A=0A=0A=0A      
--0-912371670-1224754607=:6161--