hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathis Thomas (VTG)" <mat...@vtg.at>
Subject AW: POST method - Default content encoding
Date Mon, 03 Feb 2003 14:03:53 GMT
Is that fixed now? 
I tested this issue with HttpClient 2.0 alpha2 and the result was the same
(wrong encoding)!

-----Ursprüngliche Nachricht-----
Von: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
Gesendet: Mittwoch, 15. Januar 2003 10:22
An: Commons HttpClient Project
Betreff: RE: POST method - Default content encoding


It undoubtedly *should* be ISO-8859-1 by default. Currently system default
encoding is used regardless of the 'Content-Type' header value.

We are aware of the bug. I have already posted a patch that fixes (well,
attempts to fix) all known encoding related problems. Unfortunately, all our
committers are currently either missing in action or too busy. So, please,
stay tuned. The fix is expected soon

-----Original Message-----
From: Mathis Thomas (VTG) [mailto:mathis@vtg.at]
Sent: Wednesday, January 15, 2003 10:11 AM
To: 'Commons HttpClient Project'
Subject: POST method - Default content encoding

I think that the default encoding for a post should also be ISO-8859-1, is
that right?

With the latest nightly build I sent a post to a server with german umlauts
and these characters were endoded with UTF-8. I used following code:

PostMethod post = new PostMethod();
post.setHttp11( true );
post.setPath( "/samplepath" );
post.addParameter( "TXT", "Testtext: öäüÖÄÜß");
String s;
try {
  //post.setRequestHeader( "Content-Type", "text/plain; charset=ISO-8859-1"
  int ret = client.executeMethod( post );
  s = post.getRequestBodyAsString();
  System.out.println( "requestBody=" + s );
} catch (Exception ex ) {

The output is :
but schould be: requestBody=TXT=Testtext%3A%20%F6%E4%FC%D6%C4%DC%DF
Even if I use the outcommented line it does not change the output.

Thanks in advance,

View raw message