Search results

your css is served by php: http://certcollection.org/forum/public/min/index.php?ipbv=31007&f=public/style_css/css_16/ipblog.css this should be very inefficient. should serve it directly by litespeed: http://certcollection.org/forum/public/style_css/css_16/ipblog.css if litespeed serve...

it looks possible, but may need write php script in proper way. here's a successful story FYI: http://www.litespeedtech.com/support/forum/showthread.php?t=3322 the tech info: "it's a extremely modified copy of the php script called glype http://www.glype.com/"

please refer: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi:troubleshoot

paste the .htaccess here. any change made in recent 2-3 days ?

which is the cause, rewrite or mod_security?

maybe rewrite cause a infinite loop or loop in a mod_security rule? can disable all mod_security rules temporarily if it's the latter case. for former case, in docroot .htaccess, put rewriteengine off in first line. then access test.php again.

strange. how about phpinfo() page? 408 error as well ?

no. if php scripts only need 2-3 seconds to complete, increasing timeout won't affect these scripts at all. only affect those scripts which need above 60 seconds to complete. can you figure out which url cause 408 time out error ? or many URLs ?

it's too short. that means if a php script running over 60 seconds, lsws may think it's hanging and kill the php process, and issue 408 time out error. please check if that php script run for a long time? if it's the case, increase the time out.

what's the setting of admin console->Server->Tuning->Connection Timeout (secs)?

gcc is not installed at the box ?

the server's expire setting can be overridden by vhost or .htaccess or php script no problem found on the setting you posted. please check .htaccess or httpd.conf, if ExpiresActive off exists.

in GZIP Compression -> Compressible Types, please remove "image/*", and restart lsws

admin console -> Actions -> Version Manager

default mime type: can customize it at server level and can override it at vhost and in .htaccess.

confirmed to be a firewall issue and fixed. from customer: "there was an errant firewall rule ... That has been corrected and now the SSL encryption is going through... not LiteSpeed's SSL implementation"

maybe this line RewriteCond %{REQUEST_URI} !^/forum/(login|register|usercp|private|profile|cron|image)\.php$ not correct for your site? what's the forum homepage? domain.com/ or domain.com/forum/? p.s. what's status of the special mysql issue you mentioned last time?

admin console->Server->General->Expires Settings->Expires By Type

should be no problem at all. you can try the 32-bit linux standard version to take a test.

need add a note here for future search: they changed the php code to reduce the cookie size, and fixed 503 error. 503 is a general error, there are many reasons to cause 503.for example, if a php script fail to get enough memory, a 503 error may occur. please create a new thread for better...