https://issues.apache.org/bugzilla/show_bug.cgi?id=45187





--- Comment #8 from Roman Garcia <[EMAIL PROTECTED]>  2008-06-12 13:50:57 PST 
---
(In reply to comment #7)
> Yes.
> 
> The filename testing occurs in the "directory walk".  Any module which
> is configured to avoid this altogether, e.g. mod_proxy using ProxyPass
> redirection, should dodge the filename testing.
> 
> That's not how mod_jk works, but you should try mod_proxy_ajp as a suitable
> replacement which should solve your issue, provided you don't encounter 
> similar
> problems on Tomcat.

I will try the mod_proxy_ajp to see if that solves OUR problem. 
But still, that won't solve Apache's problem.
For whatever reason, Apache does check the filesystem to see if a given file is
there. And FORBIDDEN is not a valid response to that question.

I guess what confuses me the most is you guys don't seem to consider this issue
as a bug. Is FORBIDDEN a valid answer to a long URI request?

> Since reading the thread, and the fact that you are the first app designer
> to complain, I'd suggest a review of your design parameters to come up with
> URI paths that aren't so excessively long.  There may even be issues on the
> client side with paths such as these.

Even if I could change requirements (which I can't), I wouldn't only to adjust
them to an existing bug.
Also, I don't consider 400 chars excessively long. Specially when even worst
browsers, IE that is, support more than 2048 chars long
http://support.microsoft.com/kb/q208427
Opera & Firefox support more than 10k chars for URLs I believe...

If the problem is "how many app designers complain", just let me know so I can
collect signatures for a "formal request". Just tell me how many app designers
do you need. ;)


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

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to