You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2006/09/19 13:46:00 UTC
DO NOT REPLY [Bug 40540] New: - Bad interaction between MultiViews and SetOutputFilter
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=40540>.
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=40540
Summary: Bad interaction between MultiViews and SetOutputFilter
Product: Apache httpd-2
Version: 2.0.55
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_negotiation
AssignedTo: bugs@httpd.apache.org
ReportedBy: andy@insectnation.org
I've observed problems with specifying output filters by Location and Directory
while using Multiviews content negotiation for some time. See these mailing list
entries:
http://mail-archives.apache.org/mod_mbox/httpd-users/200606.mbox/%3c44A3D121.8010208@durham.ac.uk%3e
http://mail-archives.apache.org/mod_mbox/httpd-users/200608.mbox/%3c44D1EA1B.3030101@durham.ac.uk%3e
What it comes down to is that if Multiviews is active, then SetOutputFilter
statements in <Location> or <Directory> blocks have very flakey behaviour
(perhaps because Multiviews is rewriting whatever location string is used for
matching against Location paths?)
Presumably this isn't intentional --- both are very useful features, but it's
annoying that they don't seem to be compatible, at least not with the
configurations I've tried.
Andy
--
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 40540] - Bad interaction between MultiViews and SetOutputFilter
Posted by 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=40540>.
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=40540
nick@webthing.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From nick@webthing.com 2006-12-12 17:52 -------
Why are you using <Location> with local contents? Its semantics can be very
confusing if you start making assumptions about how it maps to your filesystem.
What happens if you use <Directory>? And what happens if you use
FilterProvider/FilterChain in place of SetOutputFilter?
Also, that kind of extfilter usage is massively inefficient. Use mod_line_edit.
--
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 40540] - Bad interaction between MultiViews and SetOutputFilter
Posted by 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=40540>.
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=40540
------- Additional Comments From andy@insectnation.org 2006-12-15 07:39 -------
(In reply to comment #1)
> Why are you using <Location> with local contents? Its semantics can be very
> confusing if you start making assumptions about how it maps to your filesystem.
What local contents? Do you mean the use of multiviews?
I'm using location because I want all HTTP content provided from a particular
URL context to be filtered, regardless of where it maps to on the filesystem,
possibly with the same content being filtered in two different ways depending on
how it's accessed. Also, some of the content which I want to be filtered comes
from CGI scripts which sit outside the document root, so explicitly mapping each
of those with a <Directory> section would be cumbersome and pointless (if,
indeed, it would even work - I've not checked).
> What happens if you use <Directory>? And what happens if you use
> FilterProvider/FilterChain in place of SetOutputFilter?
I can't test this yet, since they're only available in mod_filter from 2.1
onwards and (due to OS packaging lagging behind the times) I'm stuck with 2.0.55
for now. That looks like a much better framework, though: thanks for pointing it
out!
> Also, that kind of extfilter usage is massively inefficient. Use mod_line_edit.
That was a demo! I have no real-world interest in replacing "foo" with "bar"
(but I do have an interest in applying e.g. uniform, dynamic headers and footers
to all the content on my site without having to worry about the
languages/proxies/etc. that each bit is implemented with, which is what this is
really all about.)
Thanks for the comments, though, especially the pointer at FilterChains etc. I
still think this is a bug, though: I'm not convinced that the argument about
local content applies here.
--
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org