Martin Schnyder wrote:
When I use the GetMethod class to send text with special characters (German
Umlaute "äöü") in the request parameters, the special characters are not
encoded correctly. This happens when I use method
HttpMethodBase.setQueryString(NameValuePair[] params)
to set the query parame
Laura,
Good link information! ;)
Sung-Gu
The more modern approach is to assume that the URI is always in UTF-8. If there are
any non-ASCII characters in it after URL-decoding, then you run it through a UTF-8
converter (UTF-8 to UTF-16 in the case of Java). Here's a proposal on this:
http://w
Strange Thing!
I have lucky version of httpClient because I solved my problems with
URI.setDefaultProtocolCharset(CHARSET)
For GET and POST methods.
I forgot to say that I've changed the system property LANG for the jvm start
script
LANG=es_ES.ISO8859-15; export LANG
It works fine with Ñ characte
mons HttpClient Project
Subject: Re: Encoding of special characters in request URI
This is one of many 'shady' areas of the HTTP spec. Basically there is
no standard way for the client to communicate to the server what
coding
has been used to decode query parameters. I believe some browser
gt; From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> > Sent: Donnerstag, 10. Juli 2003 19:12
> > To: Commons HttpClient Project
> > Subject: Re: Encoding of special characters in request URI
> >
> >
> > This is one of many 'shady' areas of the HTTP spec
be use as
default) or if there would be an other way to specify a different charset.
Martin
> -Original Message-
> From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 10. Juli 2003 19:12
> To: Commons HttpClient Project
> Subject: Re: Encoding of special
That's quite a handy reference. Thank you for the info Laura.
Mike
On Thursday, July 10, 2003, at 03:35 PM, Laura Werner wrote:
Oleg Kalnichevski wrote:
This is one of many 'shady' areas of the HTTP spec. Basically there is
no standard way for the client to communicate to the server what
codi
From RFC2396:
For original character sequences that contain non-ASCII characters,
however, the situation is more difficult. Internet protocols that
transmit octet sequences intended to represent character sequences
are expected to provide some way of identifying the charset used,
Oleg Kalnichevski wrote:
This is one of many 'shady' areas of the HTTP spec. Basically there is
no standard way for the client to communicate to the server what coding
has been used to decode query parameters.
It's definitely shady. I've seen two approaches used here. In the
past, many internat
This is one of many 'shady' areas of the HTTP spec. Basically there is
no standard way for the client to communicate to the server what coding
has been used to decode query parameters. I believe some browsers use
'Accept-charset" or 'Accept-Language' headers to negotiate the locale
settings to be u
Hello Martin,
This is a good question, one that I am not positive I know the answer
to. The HTTP request line (containing the query params) must be
US-ASCII. That I am sure of. The catch is that form urlencoding
strings makes them ASCII, regardless of the original charset. So
HttpMethod.se
-Mensaje original-
De: Martin Schnyder [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 10 de julio de 2003 16:23
Para: [EMAIL PROTECTED]
Asunto: Encoding of special characters in request URI
When I use the GetMethod class to send text with special characters (German
Umlaute "äöü") in
When I use the GetMethod class to send text with special characters (German
Umlaute "äöü") in the request parameters, the special characters are not
encoded correctly. This happens when I use method
HttpMethodBase.setQueryString(NameValuePair[] params)
to set the query parameters.
I saw that Relea
13 matches
Mail list logo
