Search results

I'm the wrong person to direct your criticism to. I've been working with LSWS for more than 10 years and have learned my lessons that the rules of the game are just a little different with LSWS|OLS. Accept these rules of the game or wear yourself out by them. In the end you can't change anything...

That's an honor, but things are a little different in sales and marketing.

That doesn't necessarily mean that LiteSpeed is doing something different or wrong. It has turned out in recent years that Apache has not adhered to the RFC.

Do you also believe in Santa Claus or the promises of advertising? ;)

Forget Apache. With LSWS|OLS the rules of the game are a bit different. ;)

No, it doesn't, at least not with me and if I append headers in .htaccess and with LSWS.

Header append does the same and is the preferred method to add headers with the same name, at least with LSWS.

Congratulation, but use this link: ;) https://store.litespeedtech.com/store/aff.php?aff=320

Okay, dump OLS and use LSWS instead.....

Did you ever set a simple test header like:? header set x-testheader "test" I remember an issue with LSWS in the past where I couldn't set a header because LSWS wanted to get header append instead of header set. I just can't imagine OLS refusing to set a header?!

I think you should check OLS configuration....

Domain limit: >>>> 1 <<<<<

Number of workers is secondary. You must care about the available RAM. Starter license has a 2 GB limit!!!

Sorry, can't believe that. Setting a header in .htaccess belongs to the basic of the basics.

or this? Works with LSWS RewriteCond %{REQUEST_URI} \.(svg|xml?.)$ RewriteRule ^.*$ - [ENV=HEADERS:true] Header set Cache-Control "public,max-age=2592000" env=HEADERS

And this? It works with LSWS. SetEnvIf HEADERS ^ HEADERS SetEnvIf Request_URI "\.(svg|xml?.)$" !HEADERS Header set Cache-Control "public,max-age=2592000" env=HEADERS

What about this? <FilesMatch "\.(svg|xml)$"> Header set Cache-Control "public,max-age=2592000" </FilesMatch>

Yes, where else? ;) LiteSpeed supports it, but as already said, it is limited. With the last update, the compatibility with Apache was extended, at least with the LSWS. Unfortunately, I don't know whether this range of functions was also implemented in OLS.

Litespeed (LSWS and OLS ) supports expressions but limited and it is not fully Apache supported. https://httpd.apache.org/docs/2.4/expr.html#examples

The big LScache fail report for LiteSpeed LSCWP and all other LiteSpeed cache plugins https://www.litespeedtech.com/support/forum/threads/the-big-lscache-fail-report-for-litespeed-lscwp-and-all-other-litespeed-cache-plugins.21053/