You will still need to fix the actual parameter parsing routine to delay
applying the encoding until the name and parameter are parsed out of the
input stream...
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 12, 2001 1:14 PM
Subject: Re: charset used for parameters decoding on HTTP request
Tomcat3.x,4
> > I would like to know the policy for the request's parameters decoding in
> > Tomcat 3.x.
>
> AFAIK there are still problems in both 3.2.x and 3.3(dev). Fixing this is
> one of the highest things on my todo list, and you should expect a
> solution before 3.3 beta ( i.e. in about a month ).
>
> The solution will likely use a special module that will try to "guess" the
> encoding using the common hints ( Content-Type, Accept-Language, the
> common solution of passing a charset parameter ). It is not possible to
> use the setCharset() method from Servlet2.3 - but in most cases you'll not
> have to.
Good Idea.
BTW, Netscape navigator 4.7x seems to return the charset header value when
it is not the same as the default encoding.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
