I know that you can set custom headers there, but it does not support setifmepty. I am asking whether there is an alternative approach I can use with OLS, that would simulate this somehow?
I know that, but I can't apply any conditions there, aside from directory root. And, to be honest, migrating a couple of dozens of rules from Apache into separate contexts, even if they rules were based on directories, seems like an extreme chore
Hm... Does it really read the headers from .htaccess, though? I tried just "Header set x-test-htaccess true" (for test purpose) and
<IfModule headers_module>
Header set x-test-htaccess true
</IfModule>
But the header was not added, even though, I know that .htaccess file was read, since to...
Do I have to use them in an .htaccess file specifically? Because I've tried IF conditions in "Context" module's headers and it did not work: OLS generated headers with those names, instead.
Are Litespeed's differences in expressions support documented somewhere?
Is there a way to set headers based on some condition? In Apache I could use <IF> statement or something like
set Cache-Control "max-age=2592000,public" "expr=%{CONTENT_TYPE} =~ m#image/svg\+xml#i"
but I do not see a way to do that in OLS. Or am I missing something?
"Header operations" tell that they support "condition" same as Apache's mod_headers. Apache's module supports "always" and "onsuccess" condition, but looks like OLS does not recognize "onsuccess" condition, instead creating "onsuccess" headers:
Granted, in most cases using "always" should be...
I am not sure if it's a bug or I am doing something incorrectly, but it looks like when I try to use "merge" for custom headers (through "Context" feature), instead of merging the headers, it appends the new values.
Simplest example, which does work in Apache: I want to ensure that "Vary" header...
"/httperror/404" is not a physical page, it's a page generated by "index.php", if the URL of the actual page is "/httperror/404" or if a 404-like error is triggered internally in the script.
Custom error pages are already setup like shown below:
With current setup, if I remove the custom page...
Hi!
I have a setup, where through rewrite rules on "/" context level I direct [almost] everything to index.php file, where I process the "route" in URL, that is "/fftracker/search/" for example will be processed by the main PHP script and content will be shown based on the logic designed...
Hi!
I have a setup, where through rewrite rules on "/" context level I direct [almost] everything to index.php file, where I process the "route" in URL, that is "/fftracker/search/" for example will be processed by the main PHP script and content will be shown based on the logic designed...