Search results

Try a rewrite rule like RewriteRule Uxi6h - [E=blockbot:1]

It is in the default now, just the old installation will not pick it up, only new installation will. ask your ISP again see if they could, there is no harm adding another one to the list.

Please check output ls -l /usr/local/lsws/bin if lshttpd is pointing to lshttpd.4.2.10 , it has been upgraded. try /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.10 again to get latest build. Maybe you need to a full stop/start. do killall -9 litespeed /usr/local/lsws/bin/lswsctrl start

Please try the latest build of 4.2.10 again, /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.10 The problem should have been addressed in latest build.

This has been addressed in latest 4.2.10 build.

One related bug has been fixed in the latest 4.2.10 build, please do a force reinstall and try again.

It is an internal state for the connection, should not happen under normal situation. Maybe you have incoming bandwidth throttling enabled? If yes, you can ignore this log message. We need to avoid this log message as it is normal if incoming bandwidth is throttled.

/usr/local/lsws/bin/lshttpd.4.2.9 should be created if you upgrade successfully. you can run install.sh to upgrade manually.

You need to check the core file with GDB to find out why PHP crash. For log rotation, server restart will trigger log rotation if you did not set http://www.litespeedtech.com/docs/webserver/config/general#disableInitLogRotation

It is fixed int the latest 4.2.9 build, just run command /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.9

Yeah, we will add that MIME to the default Compressible Type configuration.

the Apache AddOutputFilterByType directive is not supported by LiteSpeed yet. what should be compressed is configured with LSWS native configuration at server level, usually do not need to be changed.

The default error pages has been updated in latest build of 4.2.9, just do a force reinstall, should looks better. We will add the feature to allow people customize the default error page, maybe in our 5.0 release.

You need to add "image/svg+xml" to http://www.litespeedtech.com/docs/webserver/config/tuning#compressibleTypes

Fixed now.

FYI, It more likely an APC configuration issue for the PHP ProcessGroup of that account. PHP error_log have entries like "PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0" which is from APC cache, php.ini tuning may take care of it.

You need to raise LVE limit to allow two running instance of litespeed during a server graceful restart. If the limit has been reached by PHP processes started by the previous instance of litespeed, the newly started litespeed instance could not start any PHP process. Raise LVE limit to give...

both Ignore Request Cache-Control Ignore Response Cache-Control should be set to yes. whether to use cache is only controlled by rewrite rule. If still have problem, may need to turn on rewrite logging and debug logging to find out why cache was enabled.

Make sure lshttpd is running. try "curl http://localhost:7080"

When it happen again, please do killall -USR2 litespeed to turn on debug logging dynamically, the "Log Level" need to be set to "DEBUG" before hand. Send a request to reproduce the problem, then grep your IP in /usr/local/apache/logs/error_log. send the grep result to bug@litespeed...