Search results

>when we switch to ProcessGroup and PHP suEXEC to "No" even in ProcessGroup mode, should set PHP suEXEC to "Yes" document: http://www.litespeedtech.com/products/litespeed-sapi/php/suexec-processgroup but maybe it's better to mention set PHP suEXEC to "Yes" here this wiki page...

the cache policy has problem. change Cache Request with Cookie No Cache Response with Cookie No Ignore Request Cache-Control No Ignore Response Cache-Control No to Cache Request with Cookie Yes Cache Response with Cookie Yes Ignore Request Cache-Control Yes Ignore Response Cache-Control Yes you...

please change RewriteRule ^$ - [E=cache-control:max-age=9600] to RewriteRule ^.*$ - [E=cache-control:max-age=9600]

the complete command is: #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.0

Please post your whole .htaccess here(if not too long).

no need. lsphp is same.

replied PM. not able to reproduce the issue in my Chrome. still in conversation.

have you tried latest 5.0 build ? if not, please re-install the latest one, maybe many issues already resolved. if issue still exist, then revert back to previous version. #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.0 to force-reinstall to latest build

click on my username, in the pop up window, click "Start a Conversation"

maybe you refer the directory index page. this wiki is for you: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:autoindex

I'd login the server for more tests, to address all current issues and possible new issues

#curl -I youdomain.com and check the Server response header. for example: #curl -I www.litespeedtech.com HTTP/1.1 200 OK Date: Sun, 03 May 2015 03:00:59 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 X-Powered-By: PHP/5.4.38 Set-Cookie...

while cache policy is same, querystring/cookie/request or response cache-control vary for different vhost. so your case may be normal, not bug. need more info to know if it's an issue or not.

it's safe -- you can switch back to previous version by one-click and some users has run it in WHM/cPanel production environment.

while it may be set up correctly and finally get it work, I'd not recommend anyone running this in production environment. this option has been there many years ago and at that time chroot seems to be a hot-topic technology. but unfortunately it hasn't become popular at web server level. one...

yes. but 5.0 still there but not running. so it's easier to switch between versions.

how about connect to lsws directly, bypass CDN ?

I tested with the rules: RewriteEngine On RewriteRule .*\.(jpg|jpeg|gif|png|bmp|JPG|JPEG|PNG|BMP|GIF)$ http://www.domain.com [R,NC] RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC] RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC] no other rules -- in .htaccess it works as expected -- a access...

tested with 4.2.23 in .htaccess, above rules works as expected. using #curl -k -I https://youdomain.com to test. note: above rules should put at the beginning of .htaccess, otherwise it may not be reached.

general guide for 503 error: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors in your case, if ZendGuardLoader, Suhosin is enabled, try to disable them(if feasible), and see if any improvement.