Tim's right, you should ALWAYS use encodeURL from the beginning of your
project--it doesn't take much effort and it will save you heartache in the
future. And it's part of the Servlet spec, who knows if they will use it
for something else in the future.
Or even better, create your own method that wraps encodeURL, so that in the
future you can further rewrite the URL for your own purposes... for example:
<% ResponseEncoder re = new ResponseEncoder(response); %>
<a href="<%= re.encodeURL("page.jsp") %>">link</a>
(where ResponseEncoder.encodeURL() calls response.encodeURL())
And I don't believe that ANY servlet container supports automatic rewriting,
nor should it--at least not by default. That would require a
post-processing step that doesn't exist within the JSP/servlet world.
-jmc
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://archives.java.sun.com/jsp-interest.html
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.jsp
http://www.jguru.com/faq/index.jsp
http://www.jspinsider.com
