Search results

Sorry, this is not great. Offering a CLI variant of crawler is an option, but not the one and only option. This option is intended to run in cronjob, but is only a small part of complex application with a lot of features and functions. This comment is like a knockout for LiteSpeed Enterprise...

For testing and debugging I have the crawler script extracted from main application to get it work in CLI. For this test there is no custom connection timeout in .htaccess defined. The crawler is running without interruption until script it is finished, but only in CLI! To me, it looks like...

Support for OpenLiteSpeed -> https://forum.openlitespeed.org/

Okay, but also need No CLI support.

Not yet, but is on to do list It won't bother? Can you explain that?

For testing crawler warmup the cache for other domain.

No. assets.php -> curl

FYI: QUIC is only supported by Chrome and Opera browser.

You are welcome :)

No, sorry.

QUIC is part of HTTP/3. Enable QUIC and you will get HTTP/3. If done, check at https://http3check.net/ if it works. (powered by LiteSpeed)

Has noconntimeout directive any limitation so it can't be used for $_POST?

Testcase? Hm... I try to explain... I developed a PHP based multi-threading crawler for cache warmup. It works as it should and with all options (similiar to crawler in WP cache plugin, but x-time faster). Everything is okay, but there is still a problem with connection timeout. I can set time...

@NiteWave I have tested noconntimeout and noabort directives, but it doesn't work! So what is wrong?

There is no special configuration that takes influence to TTFB, but you should enable QUIC to reduce time for SSL handshake.

As announced from Google last year Google will include Page Experience signals into Google search ranking. A good time to think about what must be done not to be punished and not to loose good rankings if a page is too slow. It is also Google's plan to "pillory" pages that are too slow if they...

You didn't read what the reported issue is about. There is nothing multiple, neither multiple cookies nor multiple values. The issue with multiple values never exist in LiteSpeed Enterprise.

Basically yes, but not in this case. This case is completely different. It is not about multiple vary values for cache vary cookie.

Thumbs up! ;)

Why don't you try it and use the cookie for RewriteCond exactly how it is generated? You already lost and you can only win if you try it. To me, _ls_cache_vary_ is a prefix and needs the cookie name as suffix to complete the cache vary. How long does it take to change RewriteRule? 5 seconds? ;)...