httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Buckley <>
Subject [users@httpd] SetOutputFilter doesn't work in <Location>s?
Date Thu, 29 Jun 2006 13:09:53 GMT

(Before I begin: I sent two messages on a similar topic to this a couple 
of weeks ago but got no reply: can someone please give me some feedback 
on whether I should report this issue as a bug or if it is my fault?)

I have a long-standing problem with getting Apache 2 output filters to
work on a per-<Location> basis. As far as I can tell, the
SetOutputFilter directive either doesn't work in <Location> blocks, or
is quite unpredictable in that context. I sent a test configuration in a 
previous email but recieved no response, so I've produced a simpler 
configuration and tested it on a different system, with the same 
results. Here's the configuration fragment:

     DocumentRoot /www/filtertest

     #SetOutputFilter a;b

     <Location />
         Options Indexes FollowSymLinks MultiViews ExecCGI
         AllowOverride None
         Order allow,deny
         Allow from all
         DirectoryIndex index

     ExtFilterDefine a mode=output intype=text/html outtype=text/html
cmd="/bin/sed -e s/foo/bar/g"
     ExtFilterDefine b mode=output intype=text/html outtype=text/html
cmd="/bin/sed -e s/bing/boom/g"
     <Location /a>
         SetOutputFilter a
     <Location /b>
         SetOutputFilter b
         #Order deny,allow
         #Deny from all

The results of using this configuration are as follows:

   * The sed replacements take place neither in
   * If the Location /b access is denied (by uncommenting the Order and
Deny statements), this is correctly reflected in the browser behaviour
   * If the SetOutputFilter at VirtualHost level (i.e not in any
Location blocks) is uncommented, the sed replacements both take place
as expected

So, the problem is not the Location matching because the access denial
works as expected: there seems to be some problem specifically with
SetOutputFilter used on a Location basis. This is observed using Apache
2.0.55 as packaged in Ubuntu Dapper:

andy@dirac:~$ apache2 -v
Server version: Apache/2.0.55
Server built:   May 29 2006 01:52:53

I've also observed the same behaviour in Scientific Linux 4.x. Can
anyone offer any suggestions / try this config for themselves and
comment. If it's a genuine problem then it should be reported as a bug,
but I'm not aware of any independent confirmations. Some assistance, please?


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message