DO NOT REPLY [Bug 20946] - Can't specify filter order when combining AddOutputFilter and SetOutputFilter

[bu...@apache.org]

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20946

Can't specify filter order when combining AddOutputFilter and SetOutputFilter





------- Additional Comments From trawick@apache.org  2003-07-12 00:46 -------
if you use ftype argument to ExtFilterDefine, you can override the default
placement of your external filter.  Normally it is defined as a resource filter,
just like mod_include's filter.  If you define it as something that comes after
resource, then mod_include will necessarily come before it.

Try this modified directive:

ExtFilterDefine htmlparser mode=output cmd=/bin/cat intype=text/html ftype=11

11 is 1 more than AP_FTYPE_RESOURCE, so the htmlparser filter would have to come
after any resource filters such as the INCLUDES filter.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org