AW: POST method - Default content encoding

: Re: POST method - Default content encoding Patch applied. Thomas, please let me know if that fixes the problem for you Cheers Oleg PS: my apologies for mixing up your first and last name On Mon, 2003-02-03 at 19:41, [EMAIL PROTECTED] wrote: > All right. We did talk about different thi

Re: POST method - Default content encoding

Patch applied. Thomas, please let me know if that fixes the problem for you Cheers Oleg PS: my apologies for mixing up your first and last name On Mon, 2003-02-03 at 19:41, [EMAIL PROTECTED] wrote: > All right. We did talk about different things. Now I see the problem. Whoever >initially progr

Re: POST method - Default content encoding

All right. We did talk about different things. Now I see the problem. Whoever initially programmed PostMethod did not take content encoding into consideration when performing URL encoding, and I blundered by failing to properly audit that bit of code. I'll fix it right away Thanks for pinning

Re: POST method - Default content encoding

Let me make some definitions to ensure we are talking about the same thing. There are two encodings envolved: Enc 1 Enc 2 [unicode string] --> URL encoded form > byte[] "ö" URLEnc w/ UTF-8 %C3%B6 ASCII 0x25, 0x43 ..

Re: POST method - Default content encoding

Odi, GET is an entirely different ball game. RFC is quite explicit about it: it's US-ASCII all over the place, except for request/response body. That's why it takes URL-encoding in the very first place in order to comply with the spec. Only request/response body may be encoded with a different e

Re: POST method - Default content encoding

[EMAIL PROTECTED] wrote: RFC 2616 does not seem to say much. So, I assume that the default scheme applies: whatever charset is specified in "Content-Type" header. If charset is not explicitly set, ISO-8859-1 is used per default. I guess this is the way to go for POST. But what about GET? There i

Re: POST method - Default content encoding

RFC 2616 does not seem to say much. So, I assume that the default scheme applies: whatever charset is specified in "Content-Type" header. If charset is not explicitly set, ISO-8859-1 is used per default. Do you see it differently? Cheers Oleg -

Re: POST method - Default content encoding

[EMAIL PROTECTED] wrote: Aha, it just hit me. Post parameters are url encoded, so all umlauts get escaped. If you send as a parameter value something like that: "Grüezi, Herr Thomas" You gonna get this: "Gr%C3%BCezi%2C%20Herr%20Thomas" I hope you are aware of that Oleg And which encoding s

Re: POST method - Default content encoding

Aha, it just hit me. Post parameters are url encoded, so all umlauts get escaped. If you send as a parameter value something like that: "Grüezi, Herr Thomas" You gonna get this: "Gr%C3%BCezi%2C%20Herr%20Thomas" I hope you are aware of that Oleg --

Re: AW: POST method - Default content encoding

Note, he is using *getRequestBodyAsString*, not getResponseBodyAsString. There is no echo. [EMAIL PROTECTED] wrote: Mathis, I have double-checked the code and so far I have got no reason to assume it produces errnous results. I have run a simple echo test against HttpClient test web application.

AW: AW: POST method - Default content encoding

Thanks! I modified my sample code. Result is of course the same. -Ursprüngliche Nachricht- Von: Jeffrey Dever [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 3. Februar 2003 16:58 An: Commons HttpClient Project Betreff: Re: AW: POST method - Default content encoding Just a unrelated

AW: AW: POST method - Default content encoding

ä is %C3%A4 instead of %E4 and so on. The log seems to be all right but the result isn't. Thomas -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 3. Februar 2003 17:04 An: Commons HttpClient Project Betreff: Re:AW: POST method - De

Re:AW: POST method - Default content encoding

Mathis, I have double-checked the code and so far I have got no reason to assume it produces errnous results. I have run a simple echo test against HttpClient test web application. All Umlauts appear to be doing fine there. I do not know the inner working of the CGI application you are using to

Re: AW: POST method - Default content encoding

ndet: Montag, 3. Februar 2003 15:29 An: Commons HttpClient Project Cc: Mathis Thomas (VTG) Betreff: Re: POST method - Default content encoding The encoding bug in entity enclosing methods (such as POST) has been fixed right after 2.0 alpha2 release. The problem should go away with the most recent CVS

AW: POST method - Default content encoding

C%C3%96%C3%84%C3%9C%C3%9F SHOULD BE: requestBody=TXT=Testtext%3A%20%F6%E4%FC%D6%C4%DC%DF -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 3. Februar 2003 15:29 An: Commons HttpClient Project Cc: Mathis Thomas (VTG) Betreff: Re: POST method - Defau

Re: POST method - Default content encoding

as the same >(wrong encoding)! >Thomas > >-Ursprüngliche Nachricht- >Von: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]] >Gesendet: Mittwoch, 15. Januar 2003 10:22 >An: Commons HttpClient Project >Betreff: RE: POST method - Default content encoding > > >Thomas &

AW: POST method - Default content encoding

mons 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