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=40541>.
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=40541





------- Additional Comments From [EMAIL PROTECTED]  2006-09-21 10:40 -------
1. Yes - a consequence of having to use packaged versions of Apache 2 from Linux
distributions. I'd rather be on 2.2, but it doesn't seem to be a priority for
packagers :(

2. This is arguably true, although I think the distinction is a bit blurred. I'm
trying to make a filetype be handled the same way for various bits of URL-space,
which may in fact be distributed across areas on the physical filesystem, so
doing it by Directory would be less robust against changes of the filesystem
organisation and would involve a lot of duplication. I think Location is a
neater solution in this case --- and in a lot of cases other than when
specifying file access criteria.

3. This would involve re-writing the script, and since this is meant to handle
e.g. RST files the same way across several virtual hosts, I'm not sure that can
be done in a generic way: i.e. without having to hard-code some mapping from
host names to filesystem path prefix. Yuck. Using an Action has the benefit of
(at least in principle) handling a file the same way regardless of its location.
Or that's my understanding of it, anyway :)

I'm not sure if there's a bug, either, but re-writing the string that Location
does its path matching against was very surprising to me: I would expect a
Location to match the URL by which the file was accessed rather than the path
corresponding to its internal handler.


-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to