Re: Tomcat 4.0.2 b multibyte issue.

2002-01-11 Thread Alec
The JSP spec assumes a default character encoding of ISO-8859-1 for GET/POST parameters. You will need to convert the parameter strings received by servlets/JSP pages into bytes with their character encoding as ISO-8859-1 and convert them back to Java strings with your own favorite character

Re: Servlet Caching problem

2001-12-19 Thread Alec
You may insert following code in your servlets/jsp pages to avoid proxies/browsers caching contents: response.setHeader(Cache-Control, no-store); response.setHeader(Pragma, no-cache); response.setHeader(Expires, 0); It's an annoying problem due to a dummy assumption made by IE and some proxy

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

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

2001-05-11 Thread Alec Yu
I read some code in catalina jasper, and found that: There is a setCharacterEncoding() for servlet request now; but I greped all Tomcat code, and found nowhere called it. It means, by default, Tomcat use a default encoding of '8859_1'. There is no option in server.xml/web.xml for tomcat to

Tomcat supplying JSP source code

2001-04-07 Thread Alec Smecher
source code spat out at me COMPLETELY unprocessed. (Note that there should be a content type after the GET url command, which appears to be why this is happening.) What's going on? Note: PLEASE email me any responses! I'm not subscribed to the tomcat-dev mailing list! Thanks, Alec Smecher [EMAIL