LSCache expired early than cache PublicTLL settings!?!?!?! help explain and understand [SOLVED]
- Thread starter AndreyPopov
- Start date
or lifetime of generated cache is very small (not sure)
Shared Hosting Server - I only ask hoster check or set if need. but what?
I think may be problem in:
a) x-litespeed-cache-control: public,max-age=86400 is an LSCache control header, which will be seen when the cache plugin being used.
b) When using a rewrite rule like [E=cache-control:max-age=120]to enable cache as instructed in this wiki, you won’t see the x-litespeed-cache-control header.
for separate Mobile and Safari views used .htaccess rewrite rules.
may be some incompatibility between LSCache plugin and .htaccess rewrite rules?
I think may be problem in:
a) x-litespeed-cache-control: public,max-age=86400 is an LSCache control header, which will be seen when the cache plugin being used.
b) When using a rewrite rule like [E=cache-control:max-age=120]to enable cache as instructed in this wiki, you won’t see the x-litespeed-cache-control header.
for separate Mobile and Safari views used .htaccess rewrite rules.
may be some incompatibility between LSCache plugin and .htaccess rewrite rules?
No, I don't think so. In my mind the most important and the very first way would be to isolate the reason and to find out, if the issue only happens with crawler or independently from it. For this it would be very very very important to use same UA for crawler and for manual request with browser. Otherwise you will always fail.
Independently from this I remember to many of your posts in the last 2 years. You did a lot of custom modifications almost everywhere. Maybe the reason for the issue is sitting in front of the monitor....?!
Independently from this I remember to many of your posts in the last 2 years. You did a lot of custom modifications almost everywhere. Maybe the reason for the issue is sitting in front of the monitor....?!
UAs always same!
- open /info.php and copy UA
- paste UA to field in plugin, save
- start crawler
- waiting for full recache
- check
P.S. Yes! after my posts developers add to plugin:
- Add GUI option to enable separate cache for safari browser to support webp image
- Add "Rebuild Cache for specific devices/browsers" feature and GUI option
- put htaccess file litespeed directives on the top to prevent conflict OpenLiteSpeed will not generate esi cache copy htaccess vary control value added to _lscache_vary cookie
- check mobile use journal rule if exist journal theme, and other minor fix for openlitespeed, thanks for @AndreyPopovNew contribute the code
- cli crawler allow 127.0.0.x server address
- If cookie not enabled do not set _lscache_vary
- recache add manufacture urls
- optimise cache vary value for mobile view
- recache product pages will crawl up to 5 layer of categories
- recache add number of pages for product category pages
- open /info.php and copy UA
- paste UA to field in plugin, save
- start crawler
- waiting for full recache
- check
P.S. Yes! after my posts developers add to plugin:
- Add GUI option to enable separate cache for safari browser to support webp image
- Add "Rebuild Cache for specific devices/browsers" feature and GUI option
- put htaccess file litespeed directives on the top to prevent conflict OpenLiteSpeed will not generate esi cache copy htaccess vary control value added to _lscache_vary cookie
- check mobile use journal rule if exist journal theme, and other minor fix for openlitespeed, thanks for @AndreyPopovNew contribute the code
- cli crawler allow 127.0.0.x server address
- If cookie not enabled do not set _lscache_vary
- recache add manufacture urls
- optimise cache vary value for mobile view
- recache product pages will crawl up to 5 layer of categories
- recache add number of pages for product category pages
Finally and to extend your knowledge about economically cache warmup, read the following documentations. There is definitly no need to warmup the cache for Google bot and/or to define cache rules for Google or any other bot to get better Pagespeed score. It may irritate, but I have disabled cache function for any bot!
https://developers.google.com/web/tools/chrome-user-experience-report
https://web.dev/user-centric-performance-metrics/
https://web.dev/chrome-ux-report/
https://developers.google.com/web/tools/chrome-user-experience-report
https://web.dev/user-centric-performance-metrics/
https://web.dev/chrome-ux-report/
@serpent_driver
specially for you
I purge(clear) all lscache for bots 07.01.2022
now GSC statistics:
you can compare with statistics when lscache generated for bots
https://www.litespeedtech.com/suppo...help-explain-and-understand.20367/post-118507
specially for you
I purge(clear) all lscache for bots 07.01.2022
now GSC statistics:
you can compare with statistics when lscache generated for bots
https://www.litespeedtech.com/suppo...help-explain-and-understand.20367/post-118507
First of all you have to know is, that Pagespeed doesn't measure the loading time. It measures the "display time" after all data has been loaded from the server. LiteSpeed cache is speeding up the loading time, but not the display time, because only the php based main document is affected from caching but not static sources like .css or .js. These static sources and the way how the are loaded affect the display time Pagespeed is interested in. For Pagespeed it doesn't matter if a HTTP cache is used or not, because and again Pagespeed can't and doesn't measures the loading time.
If you allegedly have disabled caching for bots and if you get bad results now some other things must be wrong with your cache varies. Litespeed cache has almost no effect to Pagespeed.
Believe it or leave it....
If you allegedly have disabled caching for bots and if you get bad results now some other things must be wrong with your cache varies. Litespeed cache has almost no effect to Pagespeed.
Believe it or leave it....
you really believe in this?
first time attempt(no lscache, X-LiteSpeed-Cache: miss )
Reduce initial server response time
second time attempt and next attempts (lscached, X-LiteSpeed-Cache: hit )
and next: on Page Experience score GSC use Google Bot UA instead PageSpeed(Lighthouse) UA.
you can see this in your php response log!
first time attempt(no lscache, X-LiteSpeed-Cache: miss )
Reduce initial server response time
second time attempt and next attempts (lscached, X-LiteSpeed-Cache: hit )
and next: on Page Experience score GSC use Google Bot UA instead PageSpeed(Lighthouse) UA.
you can see this in your php response log!
Last edited:
and probably I find where problem with "LSCache expired early than cache PublicTLL settings"
after two week discussion hoster finally admitted that:
- stored lscache in system root
- delete(clean) lscache from system root to prevent overload (in unexpected for me time)
when I ask to store lscache in my account hoster says: OLS has not technical possibility
I send link to
https://openlitespeed.org/kb/openlitespeed-cache-module/
Set up Virtual Host-Level Cache Settings
hoster says: exist possibility of security breach because cache stored by web-server owner (not user account owner)
now hard discussion with hoster continues
after two week discussion hoster finally admitted that:
- stored lscache in system root
- delete(clean) lscache from system root to prevent overload (in unexpected for me time)
when I ask to store lscache in my account hoster says: OLS has not technical possibility
I send link to
https://openlitespeed.org/kb/openlitespeed-cache-module/
Set up Virtual Host-Level Cache Settings
hoster says: exist possibility of security breach because cache stored by web-server owner (not user account owner)
now hard discussion with hoster continues