Search results

BKD === backend bkd seems to have more than only 1 meaning. e.a if I send a POST request, QC doesn't support caching of POST, but the origin host is able to cache POST, but QC sends bkd header in case of POST. No, it means the opposite. Request goes to the origin server, independently what the...

Yes, this confirms what I already tried to make you understandable. x-litespeed-cache header from origin host must be hit if warmup with M2-crawler.sh would work. Warmup of a single QC node doesn't make any sense. Cache at the origin host must be warmed up first to benefit of QC CDN cache and...

If warmup would work with M2-crawler.sh and QC you would get either hit or no status header from origin server, so Latvia don't have a Internet that can switch off gravity. ;) In M2-crawler.sh there is no code that uses the IP address of the origin host to connect origin host, so curl request...

Are you sure because this is not technically possible or does the internet work differently in Latvia?

@edmundspriede With quic.cloud you can't use M2-crawler.sh to warmup the cache. This script doesn't support CDN usage, so you always warmup the cache at QC node that is closest to the origin server, but not the cache at the origin server. In addition, QC does not support cache varies defined by...

@httpd_config.conf If you change the port for SSL you will loose QUIC feature, because OLS and LSWS expect port 443 for QUIC.

@SeikoSEO This is not a rewrite issue with OLS. Check the rewrite rules added by WebP Express. It redirects to a PHP file to convert jpg|png to webp, but if a page is cached there is no PHP.

To understand what this issue is about, simply run the code below. This code increases the memory by 1 MB with each run, but the script is terminated prematurely and before the max_memory_limit is reached because it is supposedly exceeded. Observed under LSWS/OLS and PHP 8.1. <?php...

RewriteCond %{SERVER_PORT} !^443$ RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L] RewriteCond %{HTTP_HOST} !^www\. RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

Additional, QUIC will no longer work.

As far as I know OLS and LSWS only supports MaxMind GeoIP2 format database: https://www.maxmind.com/en/geoip2-databases

@miyojin You should use LScache plugin support at WordPress support forum. This issue is not a OLS issue. https://wordpress.org/support/plugin/litespeed-cache/

Why did it take almost 4 weeks? In view of the fact that the responsible developer of the Cache Plugin is a LiteSpeed freelancer, I recommend switching to LSWS. This does not solve the problem, but with LSWs you can make sure that LScache works for MediaWiki. Nevertheless, the problem with...

I'm sorry, but I don't think the proxy configuration will solve the problem. Otherwise, purging the cache using the native PHP purge header would not work. I see the problem in the IP addresses used, which are not public IP addresses. The purge function of the cache plugin is an HTTP request...

I don't think so. Purging the cache with this custom condition will work in a native environment, but not if the cache has to be purged by a cache plugin like LSCWP. @Big Boss What happens if you purge the cache by using x-litespeed-purge header and executed in related user/domain? <?php...

I support LiteSpeed, but I don't support LiteSpeed's mentality, so nothing for thank for.

How to block unwanted traffic easily but effectively and without WAF or CloudFlare. I have been working on the topic of how to block unwanted traffic, i.e. bad bots etc., for several years when PHP is not available due to LScache. The same applies if a Wep Application Firewall or CloudFlare is...

Although ESI is not supported by OLS, the following description may encourage you to use LiteSpeed Enterprise instead of OLS. OLS and LSWS are similar if not identical in many ways. In terms of performance, there are certainly few disadvantages to OLS. This also applies if you use a CMS where...

Response headers are not request headers. The RFC specification refers to response headers. Browsers send request headers in upper case for traditional reasons. If the specification states that response headers must be lower case, then you should not expect LiteSpeed to deviate from this...

@zEitEr https://www.rfc-editor.org/rfc/rfc7540#section-8.1.2 https://www.rfc-editor.org/rfc/rfc7540#section-8.1.2.6