Tomcat
12 Documents
- java.net.BindException: Address already in use:8080 ... uhm, who's listening? - Java-Monitor Forum
2010-02-11
- FAQ/CharacterEncoding - Tomcat Wiki
The fact is: there is no char encoding in a GET request. So an unmodified installation of Tomcat will parse the URI in a GET as ISO-8859-1 ("the Servlet spec requires it"). But a SPARQL request, for instance, requires it to be UTF-8 encoded. So it can't work!!!
Tomcat people insist that their behavior is a feature. Maybe it's not a bug, but I doubt it is a feature. To get tomcat working otherwise, you have to set a parameter in the server.xml (connector, URIEncoding) What if you don't control the tomcat install? Maybe the best thing to do is to parse the parameters from request.getQueryString(). In my web apps until now, I double UTF-8 encode the params in a GET (for instance, the semanlink bookmarklet)
2008-10-12
- Java UTF–8 international character support with Tomcat and Oracle, 26/03/07, Kieran's blog
2008-10-11
- Tomcat - Bug 23929 – request.setCharacterEncoding(String) doesn't work
2008-10-11
- How to get international unicode characters from a a form input field/servlet parameter into a string?
2008-10-11
- EclipseZone - Problems publishing webapp to Tomcat ...
2007-10-22
- Tomcat 5 - Documentation Index
2006-09-15
- Server Configuration Reference - The Context Container
2006-09-13
- Configuring Tomcat's URI encoding
By default, Tomcat uses ISO-8859-1 character encoding when decoding URLs received from a browser.
2006-09-12
- General purpose build script for web applications and web services
including enhanced support for deploying directly to a Tomcat 5 based server.
2006-09-03
- The Glove Compartment » Tomcat 5.5, mod_jk, and OS X’s built-in Apache
2006-01-22
- Sysdeo Eclipse Tomcat plugin
2006-01-07
Preferences...