RE: Issue in sending Request/response http headers containing Japanesecharateres

["Caldarale, Charles R" <Ch...@unisys.com>]

> From: André Warnier [mailto:aw@ice-sa.com] 
> Subject: Re: Issue in sending Request/response http headers 
> containing Japanesecharateres
> 
> > java.net.URLEncoder.encode(text, "ASCII")
> > You'll get a string like 
> > "foobar%45%67%65%43%45%45%78%69...".
>
> Yes, but in my humble opinion you would be, as they say, 
> "cruising for a bruise".

That's "cruisin' for a bruisin'", to be precise.

I think Chris meant:
    java.net.URLEncoder.encode(text, "UTF-8")
which is what W3C recommends.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

RE: Issue in sending Request/response http headers containing Japanesecharateres

[Rajat Gupta05 <Ra...@infosys.com>]

Thanks everyone for there comments.



I was actually comparing the behavior between IIS and Apache, since IIS(5/6) is able to handle Japanese characters inside the headervalues not the header name.



Thanks

Rajat



-----Original Message-----
From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
Sent: Thursday, March 19, 2009 6:56 AM
To: Tomcat Users List
Subject: RE: Issue in sending Request/response http headers containing Japanesecharateres



> From: André Warnier [mailto:aw@ice-sa.com]

> Subject: Re: Issue in sending Request/response http headers

> containing Japanesecharateres

>

> > java.net.URLEncoder.encode(text, "ASCII")

> > You'll get a string like

> > "foobar%45%67%65%43%45%45%78%69...".

>

> Yes, but in my humble opinion you would be, as they say,

> "cruising for a bruise".



That's "cruisin' for a bruisin'", to be precise.



I think Chris meant:

    java.net.URLEncoder.encode(text, "UTF-8")

which is what W3C recommends.



 - Chuck





THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.



---------------------------------------------------------------------

To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

For additional commands, e-mail: users-help@tomcat.apache.org



**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Re: Issue in sending Request/response http headers containing Japanesecharateres

[André Warnier <aw...@ice-sa.com>]

And as we recently mentioned the incompleteness of the current HTTP 
specification - at least in matters charsets - it may be worth 
remembering that it was 20 years ago, in March 1989, that a then 
little-known computer guy at CERN named Tim Berners-Lee wrote the paper 
"Information Management: A proposal", which invented HTTP and hence the WWW.
And it took still a while after that for Unicode and UTF-8 to settle, so 
we can hardly blame him for having bypassed that aspect.
So hats off, and a respectful minute of appreciation.
If he hadn't, what would we all be busy with right now ?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org