Shankar, Chris,
With reference to your previous posts
(From section 3.7.1 of the HTTP/1.1 spec).
I tried a small example by not forcing the request's content type,
and was able to see the Big5 characters without any problems even
when the Request's characterEncoding was null. The code bel
Christopher Schultz wrote:
Shouldn't you use the content-type of the request instead of just
forcing your own content-type? If the browser does not send a MIME type
with the request, then the default is defined to be ISO-8859-1:
Well, for a form post, that just means that the text of the body
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rashmi,
Rashmi Rubdi wrote:
> On 6/5/07, Shankar Unni <[EMAIL PROTECTED]> wrote:
>> (the page was already set to character
>> encoding Big5), the encoded value sent in the URL was rather screwy:
>>
>> The original character is (Big5) 0xAE 0x78.
>>
>>
On 6/5/07, Shankar Unni <[EMAIL PROTECTED]> wrote:
(the page was already set to character
encoding Big5), the encoded value sent in the URL was rather screwy:
The original character is (Big5) 0xAE 0x78.
The URL sent by IE said "%AEx". (!!)
Did you also configure the web.xml properly ?
It sho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shankar,
Shankar Unni wrote:
> One odd thing we noticed was that when we sent in a single (two-byte)
> Big5 character in a form field (the page was already set to character
> encoding Big5), the encoded value sent in the URL was rather screwy:
This i
We were playing around with a little JSP application, and trying to
submit (and handle) Big5 characters.
(The real purpose was to exercise our primary app which sniffs HTTP
traffic and "does stuff" with the raw data it captures - it sees the
headers and body as sent over the wire.)
One odd t
