DO NOT REPLY [Bug 32424] - Redirecting directiories with missing trailing slash breaks web applications

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32424>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32424





------- Additional Comments From oliverh@ourcommunity.com.au  2005-02-08 22:22 -------
(In reply to comment #4)
> In this case, Tomcat will indeed issue a redirect right away.
> Please do not reopen the issue.

Why does Tomcat redirect right away? Shouldn't the filter be given a chance to
process the original (no slash) request? 

I have an application that was previously deployed using Jetty and I'm currently
looking at moving over to Tomcat 5.5 but this is a show stopper for me. I can't
rename the directories and the end users expect the original (no slash) paths to
work. The application does not do directory listings so adding the slash doesn't
help us in the least. Is there a way to disable this?

It seems to me that this redirect should be sent by the default servlet *after*
any user filters/servlet have had a chance to process the request but then I
assume this behaviour is according to the spec? If so where is it specified?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org