-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
As Chuck points out, I really meant to encode using UTF-8. The result is
always an US-ASCII string, as per the java.net.URLEncode documentation
(really the URL Spec).
On 3/18/2009 6:51 PM, André Warnier wrote:
> If the string contained any Jap
Chris,
Christopher Schultz wrote:
[...]
there's a somewhat obvious way to encode your
headers (including Japanese or other non-ASCII characters) so they will
work:
java.net.URLEncoder.encode(text, "ASCII")
You'll get a string like "foobar%45%67%65%43%45%45%78%69...". You just
have to remembe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 3/18/2009 11:09 AM, Mark Thomas wrote:
> Go for it. Maybe as a new question along the lines of "Why does it have to be
> like this?"
Done. Now all the research I often re-do when someone asks this question
is collected in one place. I can no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/18/2009 11:15 AM, André Warnier wrote:
> So, with Japanese characters in HTTP headers, you are outside of the
> HTTP specification, and you cannot expect any webserver (or proxy) to
> handle this in any consistent manner.
>
> HTTP headers
correctly.
Thanks
Rajat
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, March 18, 2009 7:07 PM
To: Tomcat Users List
Subject: Re: Issue in sending Request/response http headers containing Japanese
charateres
Rajat Gupta05 wrote:
Hey Mark,
Thanks for yo
Christopher Schultz wrote:
> Mark,
>
> On 3/18/2009 8:57 AM, Mark Thomas wrote:
>> Rajat Gupta05 wrote:
>>> Hi All,
>>>
>>> I have a configuration where Apache(2.2) -->Mod_jk-->Tomcat(5.0) for my
>>> program.
>>> Now whenever I receive request or response having httpheaders with Japanese
>>> cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 3/18/2009 8:57 AM, Mark Thomas wrote:
> Rajat Gupta05 wrote:
>> Hi All,
>>
>> I have a configuration where Apache(2.2) -->Mod_jk-->Tomcat(5.0) for my
>> program.
>> Now whenever I receive request or response having httpheaders with Japanese
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 3/18/2009 9:36 AM, Mark Thomas wrote:
> RFC2616. You have to use ISO-8859-1.
It's worse than that: it's ASCII, not ISO-8859-1.
HTTP headers are actually delegated (in section 4.2) to RFC822
("Internet Text Messages").
HTTP section 4.2
(htt
In that case response is "??user1"
Thanks
Rajat
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, March 18, 2009 7:07 PM
To: Tomcat Users List
Subject: Re: Issue in sending Request/response http headers containing Japanese
charate
Wednesday, March 18, 2009 6:27 PM
> To: Tomcat Users List
> Subject: Re: Issue in sending Request/response http headers containing
> Japanese charateres
>
> Rajat Gupta05 wrote:
>> Hi All,
>>
>> I have a configuration where Apache(2.2) -->Mod_jk-->Tomca
proxy. Can any one provide explanation to that?
Thanks
Rajat
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, March 18, 2009 6:27 PM
To: Tomcat Users List
Subject: Re: Issue in sending Request/response http headers containing Japanese
charateres
Rajat Gupta05
Rajat Gupta05 wrote:
> Hi All,
>
> I have a configuration where Apache(2.2) -->Mod_jk-->Tomcat(5.0) for my
> program.
> Now whenever I receive request or response having httpheaders with Japanese
> charaters, those are either replaced by ??? or they are replaced by some junk
> charateres.
> Ple
12 matches
Mail list logo