Search results

  1. LiteCache

    What do I need a CDN (Content Delivery Network) for and when do I have which advantages of a CDN?

    The following explanations should help to answer the basic question of what advantages and disadvantages there are by using a CDN and whether there are alternatives. Basically, a CDN follows the principle: "Bring content closer to the user". Leaving everything else aside, everyone should be...
  2. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    And again and again, if you get 304 status code in your case and only in your case this is not a result of special settings. This is a absolute normal behaviour of every browser if he requests a static source that is not css, js or image. In your case index.html is a static source!
  3. LiteCache

    [Resolved] How to use multiple Sitemaps in Cache Plugin for Warmup Crawler?

    A few days ago there was an intense discussion in LiteSpeed Slack about why you can only enter 1 sitemap for the crawler in the cache plugin for WordPress. If you have a plugin installed, such as YOAST or Rank Math, the question does not arise because these plugins automatically create an index...
  4. LiteCache

    Alternative to LiteSpeed Cache Warmup Crawler

    *** New Features *** *** New Features *** *** New Features *** *** New Features *** *** New Features *** Since version 1.6 of the cache plugin for the LiteSpeed LScache plugin for Wordpress, there is a new function that dramatically reduces the crawl and warmup effort. While every Wordpress...
  5. LiteCache

    How to Cache POST when using LSCWP and Guestmode

    In case you are thinking of switching from OLS to LSWS at some point, I want to point out one of the many differences between the OpenLiteSpeed and LiteSpeed Enterprise web servers. The LSWS offers the possibility to cache POST requests. The OLS cannot do that. While POST is typically only used...
  6. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    LSCWP manages nothing. LSCWP is just a control panel to set cache headers. There is nothing special with this plugin.
  7. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    Of course, there must be an reduction, but it is only caused by browser cache behavior and has nothing to do with LiteSpeed and LScache. As already said, index.html at your page is identified as a static source and is not cached by LScache.
  8. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    For all interested readers of this topic, please do not use the comments of the user @kvv213 as a guide if you plan to use OpenLiteSpeed. 99% of the topics discussed here are based on insufficient knowledge of how to properly configure a server. However, using OLS does not mean additional work...
  9. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    For your information. The index.html is identified by the browser as a static file and not dynamic. That's why you can throw your supposed achievement completely overboard.
  10. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    What application are you talking about? These pictures do not show Wordpress sources?!
  11. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    Expire directive defines how long a requested source can be cached by browser, but expire is expire and not cache-control. Basically both do the same, but whenever you check response headers there must be a expire header. I can't imagine why OLS should make a Cache-Control header out of an...
  12. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    There is nothing wrong and is a typical browser behaviour, so don't care about any longer.
  13. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    The statsus code 304 for static sources depends on used browser. Chrome always displays cached CSS sources and creates a 304 status code for cached static sources regardless of which expire or cache-control settings you have made.. Firefox behavior is different. FF uses status code 200 if static...
  14. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    You should disable the setting in cache plugin for removing GET parameters. This is the cause of it.
  15. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    You seem to have not or not yet understood a few basic things. So here is an update for you. Cache-Control and Expire Directive are basically the same thing or have the same effect. The difference comes from the history of the HTTP protocol. The Expire directive originated from HTTP/1.0...
  16. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    The normal case is that etag does not have to be set, as it is set by default. The normal case refers to LSWS and Apache. Unfortunately, I don't know how this works with OLS. In the event that WP would set etags, they would have no function on cached pages. That's why we forget this option very...
  17. LiteCache

    LiteSpeed Cache prevents browsers to re-validate pages

    @kvv213 As @Cold-Egg said, your changes to etag make things worse. Above all, you are taking away an important function. Please read this: https://docs.litespeedtech.com/lscache/devguide/advanced/#understanding-response-status-codes-200-and-304
  18. LiteCache

    Alternative to LiteSpeed Cache Warmup Crawler

    Are you unhappy how to warmup the cache of your applicattion? Feel free to contact us at https//www.cachecrawler.com. We are certified official LiteSpeed Supporter and can help you in any case! LiteSpeed support
  19. LiteCache

    Alternative to LiteSpeed Cache Warmup Crawler

    @Spriteboy09 Please contact us cachecrawler.com. This forum is for OLS support. The only purpose of this empty file is to show you which version it is, otherwise you would have to install the software to find out the version number. This requirement test also has its purpose and is not...
  20. LiteCache

    htaccess noabort options not working

    It could be that noabort and noconntimeout are reserved for the LSWS.
Top