No, this is incorrect. The getCharacterEncoding() returns the encoding of the request *body*. It doesn't tell you anything about the message headers.
Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] Behalf Of Martin Holz > Sent: Wednesday, July 23, 2003 11:35 AM > To: [EMAIL PROTECTED] > Subject: Re: AW: aao > > > "Julian Reschke" <[EMAIL PROTECTED]> writes: > > > You are right that only UTF-8 makes sense (if somebody > disagrees I'd really > > see that discussed on the WebDAV WG mailing list). > > > > BTW: what do you mean by "if the client does not report a encoding"? The > > client simply can't. > > The problem occurs only, if the > HttpServletRequest.getCharacterEncoding() returns null, > which is the case for cadaver and IE5. However, if I understand > the specification > correctly, this is a bug in the client. > > For details see the thread > http://article.gmane.org/gmane.comp.jakarta.slide.devel/3311 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
