Search results

Cache-Control is still: public, max-age=3600 Cache-control for css: public, max-age=604800, no-store should be: public, max-age=31536000 Cache-control for js: max-age=31536000, public correct Cache-Control for images: public, max-age=31536000,public should be: public, max-age=31536000...

Please separate: Cache-Control is not the same as X-LiteSpeed-Cache-Control! Cache-Control is used for browser cache or caching of static sources. Dynamic sources also have a Cache-Control, but configuration for dynamic sources (the main_document) must be private, no-cache, max-age=0. The...

You have a wrong browser cache-control configuration for dynamic sources. Currently it is public, max-age=3600, but should be private, no-cache. This can cause the reported issue as the html content is cached by the browser.

Did you configure ESI for the cart in cache plugin settings?

If Journal 3 mini cart is not listed in the ESI tag selection field, you cannot use ESI for this module. As far as I know LiteSpeed doesn't support 3rd party modules like Journal 3 mini cart for OSC and you need a AJAX function to add items to the cart.

There must be no cache rule for HTML caching in CF cache configuration if you want to use reCaptcha on the origin host.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Sorry, give up. I am unable to teach you why it is not possible using LScache or/and reCapchta at the origin host with CloudFlare HTML cache at the same time. Try Gemini, ChatGPT or any other KI. But Note: Hostinger CDN cache is not the same as LiteSpeed Lscache on origin host.

Furthermore, bypassing html cache doesn't disable the CF cache. Define cache rules only for static sources!

If you are using the LiteSpeed cache, you must disable the dynamic source (or HTML) cache in the CDN (Hostinger, Cloudflare, etc.), regardless of whether reCAPTCHA is used or not. This is not a LiteSpeed-specific limitation, but a general rule. 1 cache + 1 cache ≠ 2 caches If a dynamic source...

As long as you're using a second cache layer in the CDN, reCAPTCHA simply won't work. A CDN cache doesn't recognize reCAPTCHA at the origin host and therefore caches it as well. The image shown should make this perfectly clear!

Note: 1 cache + 1 cache != 2 caches and causes conflicts, so disable Hostinger cache.

Documentation is your friend... https://docs.litespeedtech.com/

An account can have multiple domains, so you cannot disable reCaptcha in 1 single .htaccess to address all domains in a account. It must be specified in and for each document_root

Disable Hostinger CDN cache and try again.

This forum is about LiteSpeed web server related issues. For issues that are related to the LiteSpeed cache plugin for WP you better should use the LiteSpeed plugin support in WP support forum or contact quic.cloud support. This forum doesn't support the LScache plugin for WP any longer...

If you have cPanel/WHM OCSP Stapling is controlled by WHM. The OCSP Stapling configuration in LS WebAdmin is for native use if no server control panel is installed. https://docs.litespeedtech.com/lsws/cp/cpanel/ocsp-stapling/#enable-ocsp...

I didn't suggest this: RewriteCond %1 !=%{REMOTE_ADDR}

Server variables (%{REMOTE_ADDR}) cannot be used for "CondPattern" as Apache and LiteSpeed expect an expression for the CondPattern. For example, this would work: RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1$ If you really need to compare a cookie with the client’s IP, use the newer expression...