Reply-to: "Denis F. Latypoff" <latypoff@xxxxxxxxx>
Hello colin,
Tuesday, January 30, 2007, 1:36:33 AM, you wrote:
> The patch below adds SetEnvIf environment variable support that can
> be used to disable mod_xslt. Effectively, this can be used to mimics
> the functionality of XSLTAddRule but can also be used for
> dynamically assigned xslt. With this patch you can AddOutputFilter
> and then disable it based on any criteria necessary. This allows for
> more customized control over the execution of the mod_xslt module.
I am using 'AddOutputFilterByType mod-xslt text/xml'
and when my apps sends 'ContentType: text/xml' mod_xslt is processing
output document, so I can easily change content type to any other and
see non-processed document (it's for debug mainly). I don't use any
exotic mod-xslt's commands such as XSLTAddRule etc.
> This will enable the OutputFilter for all .php files (incl welcome
> pages) but disable it for the rss.php. While this is a primitive
> example, my scenario required adjustment based on Headers and
> parameters which is much more complicated for <Location> matches.
> Also this patch also moves the removal of the Content-Length to
> after the quick exit block. This is important so that pipelining is
> preserved even if the mod_xslt is dynamically removed from the chain.