Recent content by kvv213

  1. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    Thank you! I've got dzen with this already. Code 304 will work freely.
  2. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I can be wrong but it works via .htaccess
  3. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    Cold-Egg is there a manual what these parameters are doing: LiteCache do you know how LSCWP manages LSC? Some direct API requests or via text config? I'm curious about this.
  4. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    Regarding to the speed of the getting of the resources (so with 304 code we can use all the types of resources from web-server) my measurements are not very correct because the web-server is installed in Hyper-V container that is hosted at the same computer I'm sitting but we can notice a...
  5. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    OK. I did the test on my test environment with static files that includes one html and one jpg. Because we test the browser behaviour there is no difference how these files were provided by the web-server form dynamic generation or just from the disk. I was able to modify the following settings...
  6. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I did some more research including reading the manuals from google. First of all. Let's set the terminology used: 1. LSC - LiteSpeed Cache plugin. 2. LSCP or LSCWP - front face of LSC, that let to configure the LSC from WordPress admin page. In LiteSpeed httpd server LSC can be controlled...
  7. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I've started with an easy one - just static pages. And the Lighthouse picture is from the blog with the plugin just enabled (no optimization).
  8. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I'm sure that OLS moves its Expire to cache-control: These are headers from a static file (CSS) directly from OLS (not WP with the plugin). max-age=7200 is just a copy of the text/css expire setting in OLS server. expires setting tells the same. I agree with you that the best option will be...
  9. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    May I summarise my understanding taken from this thread and surfing of the specifications? I may be wrong in some cases but this is formed after some experiments with OLS: 1. Expires defines how long the resource can be considered fresh. In OLS this value is transformed into cache-control...
  10. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I've just checked with Edge, Yandex.Browser, Chrome (fresh installed). The behaviour is the same. All have the same base engine - Chromium. I receive only 200 code with normal requests with or without etag to static files like css outside of WP. If I do reload then I get 304 for such resources...
  11. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    But this is (in my screen) just a static file from OLS. Not from LSCWP.
  12. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I've just checked the static files (OLS supports etag only for static) and didn't change the behaviour it the response codes. Web-server returns the same 200 when I just load a cached static resource and returns 304 when I reload it with F5. In both cases I have a problem that the static...
  13. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    Actually OLS gives 304 code for static content like css, images and similar. Currently I've installed the following expires: image/*=A31536000, text/css=A31536000, application/x-javascript=A31536000, application/javascript=A31536000, font/*=A31536000, application/x-font-ttf=A31536000...
  14. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    OK. Some more tests: 1. I've enabled Browser cache in LSCWP. Nothing happened. I still receive 200 code, no `cache control` in headers. Pages are updated without their reload with F5. Purging all the cache didn't helped. So, the behaviour is not changed. 2. Reboot OLS-server. Nothing changed...
  15. kvv213

    LiteSpeed Cache prevents browsers to re-validate pages

    I've check this once more. 1. Regarding to eTag - there is no mentions of this in .htaccess I have for the site including WordPress site. Moreover if they were there they shouldn't be used by OLS because it works only with RewriteRule (according to the documentation). Anyway noticed some...
Top