Of course, that makes perfect sense - I had been assuming that the # was always passed to the server. But of course that's a client-side thing. An IE bug (oh joy). It's not a caching issue - the JSP displays an invokeCount just to be sure.
The next question then - is it even remotely appropriate for Tomcat to compensate? # is an illegal character in an URLEncoded string right? If so, Tomcat could (and probably should) ignore unencoded #'s (and text that follows) in the query string... ? This seems like a pretty serious problem - there are a lot of IE6 users out there. Jeff Schnitzer [EMAIL PROTECTED] > -----Original Message----- > From: Ralph Einfeldt [mailto:ralph.einfeldt@;uptime-isc.de] > Sent: Tuesday, November 05, 2002 6:20 AM > To: Tomcat Users List > Subject: RE: Tomcat bug - chokes on # when redirecting > > Have a look at the access log. > > I guess IE 6.0 passes the anchor tag to the request, > the other browsers don't. > > Tomcat doesn't know about the special meaning of > the anchor (#123) as it as client side thing. > > > -----Original Message----- > > From: Schnitzer, Jeff [mailto:JSchnitzer@;maxis.com] > > Sent: Tuesday, November 05, 2002 7:37 AM > > To: [EMAIL PROTECTED] > > Subject: Tomcat bug - chokes on # when redirecting > > > > > > What is special about a redirect from IE6?!? > > > > String go = request.getParameter("go"); > > if ("true".equals(go)) { > > response.sendRedirect("redir.jsp?foo=bar#123"); > > return; > > } > > > > foo <%= request.getParameter("foo") %> > > <a href="redir.jsp?go=true">redir.jsp?go=true</a> > > -- > To unsubscribe, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
