Eric, it is not the case. Here is the order of my loaded modules and the issue still happens (is relevant also for latest Apache version):
...
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
...
Binyamin
----- Reply to message -----
Subject: Re: Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?
Date: trešdiena, 2016. gada 28. decembris 13:20:25
From: Eric Covener <covener@xxxxxxxxx>
To: <users@xxxxxxxxxxxxxxxx>On Tue, Dec 27, 2016 at 10:29 PM, Yehuda Katz <yehuda@xxxxxxxxxx> wrote:
> Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?
>
> /sitemap.xml Response Headers shows 1 day expiration while expected to be 1
> year (1 month)
>
> Content-Type: application/xml; charset=utf-8
> Date: Tue, 27 Dec 2016 19:59:00 GMT
> Expires: Wed, 28 Dec 2016 19:59:00 GMT
>
> seems SetHandler forces it to apply text/html expiration and doesn't allow
> to rewrite it
>
> ExpiresActive On
> ExpiresDefault "access plus 1 month"
> ExpiresByType text/html "access plus 1 day"
> ExpiresByType application/xml "access plus 1 week"
>
> <FilesMatch ^sitemap\.xml$>
> SetHandler application/x-httpd-php
> Header set Content-Type "application/xml"
> ExpiresDefault "access plus 1 year"
> </FilesMatch>
It's likely just an ordering problem. mod_expires runs before
mod_headers and you can't really change it any meaningful way in this
case (you can ask mod_headers to run much earlier, but then your
scripts output will overwrite it anyway)
Presumably your script issues Content-Type: text/html which is bogus
and what's seen when mod_expires runs. A short while later,
mod_headers changes the content-type.
------------------------------------------------------------ ---------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
------------------------------------------------------------ --------- To unsubscribe, e-mail: users-unsubscribe@httpd. apache.org For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx