----- Original Message -----
From: Marco Trevisan <[EMAIL PROTECTED]>
Date: Monday, June 4, 2001 4:05 pm
> Hi Gokul,
> would you kindly specify wich containers auto-sense
> the charset for request parameters ?
I have worked with iPlanet Application server 6.0SP2 and it seems to
have the correct charset for the request parameters when run in the
international mode (a setting in iPlanet).
Also some containers behave in a manner where if you set the response
charset before asking for the parameter from the request object, the
container uses the charset specified for the response as the *default*
charset for the request. This is not a standard behaviour and there was
a small discussion on this on the tomcat developer list in the recent
past, but I do not have the link handy.
All this comes into the picture if the user-agent (browser) does not
sent the charset in the http request. It is painful to get around the
problem in version 2.2 of the API and that is the reason I think a new
method has been added in the version 2.3 of the API for specifying the
charset of the request.
Regds,
Gokul
>
> Regards,
> Marco
>
> [cut]
> > >
> > > so replace ur response.setContentType("text/html;
> > > charset=UTF-8");
> >
> > This is not supported by the servlet API. The setting of the
> charset used
> > for the response *is not required* affect the charset used by the
> container
> > for the request parameters, although some containers do behave
> in this
> way.
> [cut]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
