Hi.
I have a problem where if ExpiresByType is defined in apache config, then .htaccess ExpiresByType is ignored.
/etc/httpd/conf/httpd.conf:
/var/www/default/.htaccess:
On litespeed we see
On apache we see
If I remove ExpiresByType from httpd.conf, .htaccess successfully sets the expire time.
/etc/httpd/conf/httpd.conf:
/var/www/default/.htaccess:
On litespeed we see
On apache we see
I even tried disabling expires completely:
/etc/httpd/conf/httpd.conf:
/var/www/default/.htaccess:
On litespeed we see
On apache we see (no cache-control header at all)
I tested this on litespeed 5.0.8 64bit and and older litespeed 4.2.23 64bit, both do the same.
My litespeed config also has Enable Expires: Yes in the webserver config manager. Changing any of these settings didn't make any difference (as expected).
I have a problem where if ExpiresByType is defined in apache config, then .htaccess ExpiresByType is ignored.
/etc/httpd/conf/httpd.conf:
Code:
ExpiresActive On
ExpiresByType image/* A604800
Code:
ExpiresActive On
ExpiresByType image/* A31536000
Code:
Cache-Control: public, max-age=604800
Code:
Cache-Control: public, max-age=31536000
If I remove ExpiresByType from httpd.conf, .htaccess successfully sets the expire time.
/etc/httpd/conf/httpd.conf:
Code:
#ExpiresActive On
#ExpiresByType image/* A604800
Code:
ExpiresActive On
ExpiresByType image/* A31536000
Code:
Cache-Control: public, max-age=31536000
Code:
Cache-Control: public, max-age=31536000
/etc/httpd/conf/httpd.conf:
Code:
ExpiresActive On
ExpiresByType image/* A604800
Code:
ExpiresActive Off
Code:
Cache-Control: public, max-age=604800
I tested this on litespeed 5.0.8 64bit and and older litespeed 4.2.23 64bit, both do the same.
My litespeed config also has Enable Expires: Yes in the webserver config manager. Changing any of these settings didn't make any difference (as expected).
Last edited by a moderator: