Search results

[Solved] Script Handler pointed to wrong LSAPI For all those that have struggled with Wordpress and LiteSpeed, the problem was solved by correcting the Script Handler on the Virtual Host to point to the correct LSAPI. It was mistakenly pointed to the server LSAPI. Go to VH > Script Handler...

We've tried to enable LiteSpeed to work with WordPress but PHP continues to execute PHP as nobody or root despite setting changes. We cannot just chown nobody all the files as the server is setup for multiple users and domains. Further, the WordPress automatic upgrades are adamantly requested...

[solved] Solved and working now. Thank you.

Almost: /directory/abc/def/ghi/ ==> index.php?func=abc&urlA=def&urlB=ghi Note the last trailing slash after ghi. If it could work both ways that would be great, but, we're just trying to get it to work the one way to start as it does on Apache.

Anything contained within the first / after the base directory should be passed to the first variable, which goes to func=. Then anything in the next set of slashes goes to urlA, next set to urlB, and next set to urlC. urlA, urlB, and urlB - or their corresponding variables - might be empty...

The /directory/ folder does actually exist and is the base URL that's getting accessed. We've only changed the names here to protect the client's privacy. In the below log, /consultant/ represents /directory/ above. The results of RewriteLogLevel 9 are: Our Rules: 2012-01-17 16:26:12.830...

That did not make any difference, same results. We cut-and-pasted the quoted code directly.

[solved] With the upgrade to version 4.1.10 the issue appears to now be fixed. LSWS is returning a page without the header status. There's no doctype. But, the return value is now passing the ASV tests.

We've migrated a client to LSWS 4.1.10 Ent from an Apache environment. The site worked perfectly in Apache but now the ReWrite rules aren't working correctly. Below are the rules in the problematic .htaccess file: RewriteEngine On RewriteBase /directory/ RewriteCond %{REQUEST_URI}...

While we cannot confirm what the ASV is looking for (they won't tell us), it would be safe to assume that based on their responses that the problem is the status code 200 OK that LSWS is returning. You are correct that Apache and other servers appear to just return a blank header and just the...

That is not an option. The command line that I listed is what McAfee Secure servers are running intentionally to test the server for PCI Compliance. The actual file info.php does not exist, it's part of their test of the web server software. All of our other web servers pass the test just...

We're having trouble passing PCI Compliance testing because it seems that LiteSpeed Web Server is outputting a 200 OK header with just a title of 400 Bad Request. How can we get LSWS to stop this behavior? We have tried different LSWS versions with and without custom ErrorDocument...

We've enabled Debug logging at the Server and Virtual Host levels, restarted LSWS, and reviewed the error log. The error log does not log anything in relation to the hits/500 time out errors we're seeing on the Mac based computers. We also don't see anything logged in relation to them in the...

We've got LiteSpeed Web Server 4.0.19 installed on a CentOS 5.5 x86_64 base. A chained CA SSL certificate is installed on one of the virtual hosts as an SSL listener on the standard port 443. All Windows based browsers and clients can access the site without any problems over SSL. However...