RE: [Proposal] Default Encoding option for JSP/Tomcat in server.xml or web.xml

2001-05-14 Thread Christian Mallwitz
Hi Craig, For POST requests, the request parameters will be parsed in the character encoding specified by the browser (as part of the content type header). If they did not, a new feature in Servlet 2.3 lets you call request.setCharacterEncoding() before trying to read any request

Re: [Proposal] Default Encoding option for JSP/Tomcat in server.xml or web.xml

2001-05-13 Thread Bip_Thelin/people/razorfish
Craig R. McClanahan wrote: [...] On Sun, 13 May 2001, Alec Yu wrote: [snip] I just feel curious, why the standard specifications cost people here so much maintainance time, just because they don't allow us to specify default encodings for compilation time, input time and runtime

Re: [Proposal] Default Encoding option for JSP/Tomcat in server.xml or web.xml

2001-05-13 Thread Remy Maucherat
Craig R. McClanahan wrote: [...] On Sun, 13 May 2001, Alec Yu wrote: [snip] I just feel curious, why the standard specifications cost people here so much maintainance time, just because they don't allow us to specify default encodings for compilation time, input time and

Re: [Proposal] Default Encoding option for JSP/Tomcat in server.xml or web.xml

2001-05-12 Thread Alec Yu
From: Craig R. McClanahan [EMAIL PROTECTED] Servlet Specification 2.3 (Proposed Final Draft 2), Section 5.4 (p. 44): 'The default encoding of a response is ISO-8859-1 if none has been specified by the servlet programmer.' I am a servlet programmer also, why can't I specified it