httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Boekhold <boekh...@gmx.com>
Subject Re: [users@httpd] mod_substitute not firing with HTTP Status Code 201?
Date Mon, 17 Sep 2018 09:09:48 GMT
Hi,

Careful reading of the mod_filter documentation pointed me to the issue: 
mod_filter by default only filters documents with Status Code 200. You 
need to "SetEnv filter-errordocs" to make it work with other status codes...

Maarten


On 09/17/2018 12:14 PM, Maarten Boekhold wrote:
> Hi,
>
> I have a Substitute statement defined for a specific Location as:
>
> <Location "/my/path">
>
>     FilterChain SUBST
>
>     ProxyPass stuff
>
>     Substitute s|fromText|toText|n
>
> </Location>
>
> A specific request that is handled by this Location returns with HTTP 
> Status Code 201. The substitution does **not** take place.
>
> Another request handled by the same Location returns with 200, and the 
> substitution is executed correctly.
>
> Is there anything in mod_substitute (or mod_filter?) that is dependent 
> on the HTTP Status Code? I tried having a look at the source code, but 
> didn't immediately spot anything related to this.
>
> I found one similar question on SO about this, where a user had the 
> same issue with 403 responses, and substitution not working, so I am 
> slightly inclined to believe there is something happening here.
>
> Maarten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>


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


Mime
View raw message