Search results

Just published a new build, please try again.

Yes, it is on our road map. We are going to start LiteMage for Magento 2 development next year.

If web server is configured to trust the request header and update REMOTE_ADDR with the IP from the request header, GeoIP data will be based on the IP from request header. The key is to let Litespeed trust and use the request header to update REMOTE_ADDR.

Please do a force update to get the latest build. should be fixed.

It should work with latest 5.0.8 release. PROXY_REMOTE_ADDR environment variable are set when server update Client IP with x-Forwarded-For header. You can check a phpinfo() page to make sure PROXY_REMOTE_ADDR is set.

It was missing in 5.1RC2, please try the latest build. /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.1RC2

Sorry for the confusion, it only disables turning off mod_security from .htaccess.

https://www.litespeedtech.com/docs/webserver/config/reqfilter#disableSecHtaccess

looks like "scan post" is off. only headers are scanned. You can turn it on with "SecRequestBodyAccess" in Apache configuration.

Please try 5.1RC2 with /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.1RC2 There was a bug fixed in @fileinspect implementation. Please make sure your server log level is not higher than INFO, the modesecurity debug messages are logged at INFO level.

Image is broken. Are you talking about missing blocked requests notification in WHM? Have you checked /usr/local/apache/logs/audit_log? if a request is blocked by modsecurity, it should be logged in audit_log.

Just define a external app for each backend node, add those backend nodes to Load balancer. then update php script handler configuration to use the load balancer. The built-in load balancer does not have session affinity, requests from the same client may not assigned to the same backend node...

you can turn on Request Filter debug logging, https://www.litespeedtech.com/docs/webserver/config/reqfilter#censorLogLevel test /opt/modsecurity/bin/file-inspect.pl script manually see if works properly.

does it generate a different cookie for each page access? or it generate the same cookie again and again for the same visitor? If the cookie has to be different, litemage or other page cache wont help you much as the cost of initialize magento frame-work cannot be saved, and it is very very...

This is caused by bug introduced in LSWS 5.0, it will be addressed in next build. Anyway, browser today can tolerant that, it does not affect caching function.

then it is nothing to do with Litespeed at all.

You need to change the cache policy for the sitemap URL, not to cache it for too long.

<LocationMatch> wont match the query_string, only the URL part. So, that rule is not removed.

Please update the latest build of 5.0.7 see if it helps or not. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.7 We fixed a bug that could causes auto-logout problem when your server is behind CloudFlare.

It should be added in 1.4.13 release. Mistakenly left out in 1.4.12 release.