There was a bug like this in mod_jk prior to 1.2.5. If that's the case, then Tomcat4 won't help you since it is Apache that is serving the source (which is the usual case with this type of bug :). Try upgrading to mod_jk 1.2.5.
"Sean Utt" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hello all, I looked around on the web to see if this was a known problem, but didn't find any reference to double slash problems since 3.2. I am hoping to avoid going to tomcat4 right now because there were alot of configuration changes that I don't want to deal with, and other than this rather ugly problem, everything else is working great. I am using: servletapi3-3.3.1a-1jpp.noarch.rpm xerces-j2-2.2.1-2jpp.noarch.rpm tomcat3-3.3.1a-2jpp.noarch.rpm xml-commons-1.0-0.b2.3jpp.noarch.rpm xml-commons-apis-1.0-0.b2.3jpp.noarch.rpm and tomcat-mod-3.3.1-1 apache-1.3.27-2 What I am seeing is that a url like http://dom.ain/context/some.jsp returns the compiled page but http://dom.ain//context/some.jsp returns the source to the page where http://dom.ain/context//some.jsp does not. I would love to hear that this is a simple config problem, and to be directed a place in TFM where I might R about how to fix it. :-) Thanks! Sean Web Solutions That Work Developing custom web solutions designed specifically to accomplish the unique objectives of our clients. Phone503-639-2727 Fax503-639-0807 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
