Search results

The web server need to use the X-Forwarded-For header instead of the socket remote IP. LSWS can do that, no sure others. http://www.litespeedtech.com/docs/webserver/config/general/#useIpInProxyHeader

That's normal, the executable is /usr/local/lsws/lsphp5, ../php will be /usr/local/lsws/php, if php.ini exists under that directory, it will be used. if do not want that, just remove that configuration option, or change to absolute path.

I think 406 was the result of a mod_security rule. I could not think of any change in 4.0.1 that can cause this. maybe I can take a look at your server if you don't mind. And there is no need to reinstall from scratch, just use /usr/local/lsws/admin/misc/mgr_ver.sh to switch between versions...

Please upgrade to 4.0.1, should be fixed.

http://www.litespeedtech.com/docs/webserver/config/context/#generalContext

It looks correct. how about .php file? works as expected? Check the server level script handler configuration from LSWS console. You should have a script handler for 'php', if not, only have script handler for 'php5', then you need to change the MIME type to "application/x-httpd-php5", it must...

You need to configure the cache storage at server level from LSWS console first, then control the cache function with Apache directives CacheEnable CacheDisable CacheIgnoreCacheControl CacheMaxExpire

You probably configured the number of process of that external application too high? Show me the configuration.

that mean that info.php was not processed as PHP script. Also, make sure it is not the browser's cache trick you if you played with the configuration.

that mean php code problem, so try a simple php command like <?php phpinfo(); ?>

stop litespeed and remove the directory.

it benefit PHP suEXEC most as each PHP process use its own in memory cache, this way, just like we share a global in-memory cache.

you probably need to configure it with native configuration if you use LSWS configuration instead of httpd.conf. Just add a static context instead.

run /usr/local/cpanel/whostmgr/docroot/cgi/lsws/lsws_whm_plugin_uninstall.sh

Everything follow Linux file system permissions, no web server can get around it. If your PHP run as nobody, it will create file as nobody, if it run as the user id defined in vhost, it will create file as that user. LiteSpeed has the option to setup the permission model exactly as Apache...

Are you kidding? I doubt those forum members have the capability of fixing bug in nginx. And I doubt the nginx developer himself has the time to answer your system administration question regarding basic Unix/Linux permission questions. If you looking for answers to generic Linux...

4.1b1 has been updated to take advantage of sendfile() as well as AIO. So, on a server with low disk I/O, there is no much difference now.

LiteSpeed Web Server 4.0.1 has been released Download LiteSpeed Web Server View Version History AutoUpdate will be activated later this week, if we do not receive serious bug report about this release. :)

I don't think squid can touch LiteSpeed in this regard. No need to think about using squid for our 4.x enterprise release.

Maybe a reinstall is the solution. Need to back up your license key and serial number.