Search results

It should have been fixed in the latest debug build of 5.2 /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.2

I think it is double compression, rewrite rule redirect request to a gzip compressed version, then server compress the static file again with br. will have it addressed soon.

Would like to try a debug build on your server, it probably take less than 5 minutes to figure out what is wrong with the core dump.

There was some issue with enabling QUIC for Apache vhosts, please update to build 1 of 5.2, should have it addressed. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.2

yes, it is cached by the web server in a dedicate cache folder for compressed static files .

compressed static files are cached. some css files are dynamically generated by PHP, only compressed with gzip. for real static file, the brotli compressed version will be created on demand.

if you use hosting control panel, like cPanel, you should just follow the way to enable pagespeed as you like when Apache mod_pagespeed is used. without Apache mod_pagespeed related directive, vhosts configured through Apache configuration file wont have pagespeed enabled. Page speed is very...

For static files, it only need to compress once, so speed is not that important. We do not support brotli compression for dynamically generated page yet due it is slower speed than gzip. you have to test against a static file.

should not disable GZIP compression, not all browsers support brotli. For brotli setting, mainly the compression level, you can google the page compare the compression ratios. Brotli is slow, but it can give better compression ratio.

Have you enabled QUIC yet?

those configuration is not longer required, just make some people confused. New configuration should work fine with our cache plugin.

force update to latest 5.1.17 build, or try 5.2 . /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.17 or /usr/local/lsws/admin/misc/lsup.sh -f -v 5.2

We just follow Apache modsecurity logic, truncate the message when it is longer than 512 bytes.

please do the reinstall again. fixed a typo.

it has been updated, please try again.

PageSpeed feature is very CPU intensive, use with caution. :-)

Please upgrade to the latest build of 5.1.17, it may take care of this problem.

There is no limit on number of accounts. I think a 1-CPU license should be enough for your setup, unless there is a lot of HTTPS traffic.

Not all Magento pages can be cached, when a lot of people access the page not in cache, or not cacheable pages, the page will be served dynamically by PHP. You server has limited capacity to serve those slow magento pages dynamically, that's what you observed. you need to make you magento store...

No, we cannot do that, and it may not work that well as we cache the .htaccess, so <If > wont be evaluated for each every request, like Apache did, it re-parse the .htaccess for each request.