Search results

  1. LiteCache

    Header merge works as append

    ....because you are conditioned on Apache. Apache used to be good, but it was at least 20 years ago. So it could also be said that you are someone from the past who has slept through the present? Again, what Apache does or has done does not always comply with the RFC.
  2. LiteCache

    Header merge works as append

    Again, adapt to the situation or wear yourself out. You have every right to complain, but in the end you have to adapt to the situation.
  3. LiteCache

    Header merge works as append

    FYI: LiteSpeed is a small company with only a few employees who are constantly changing. You can hope for a lot, but expect very little. Especially no big changes. Much of what LiteSpeed does is good and follows a coherent philosophy, but the low staffing makes it difficult to change that...
  4. LiteCache

    Header merge works as append

    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...
  5. LiteCache

    Header merge works as append

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

    Header merge works as append

    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.
  7. LiteCache

    Header merge works as append

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

    Header merge works as append

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

    Header merge works as append

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

    Header merge works as append

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

    Conditional headers

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

    Conditional headers

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

    Conditional headers

    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?!
  14. LiteCache

    Conditional headers

    I think you should check OLS configuration....
  15. LiteCache

    Conditional headers

    Domain limit: >>>> 1 <<<<<
  16. LiteCache

    Conditional headers

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

    Conditional headers

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

    Conditional headers

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

    Conditional 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
  20. LiteCache

    Conditional headers

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