LiteSpeed Support Forums - Rewrites fail when using user directory in URL

LiteSpeed Support Forums (http://www.litespeedtech.com/support/forum/index.php)

- Bug Reports (http://www.litespeedtech.com/support/forum/forumdisplay.php?f=9)

- - Rewrites fail when using user directory in URL (http://www.litespeedtech.com/support/forum/showthread.php?t=6203)

Rewrites fail when using user directory in URL

Hi,

LSWS - Enterprise 4.1.13 on CENTOS 5.8 i686

I tried enabling rewrite logging and nothing showed up in the logs.
The problem does not happen with LSWS 4.1.12 and does not happen when switching to Apache

Rewrites fail when the user's directory is being used to access the page.

Here are example URLs that fail

http://123.123.123.123/~someuser/par...ge/child-page/
-- loads the page found and /parent-page/

http://123.123.123.123/~someuser/parent-page/child-page
-- Generates a 403 error

(the same errors occur when using the host name with user's directory:
http://host.server.com/~someuser/....

Rewrite Rules:

Code:

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.+)$ index.php?page=$1 [QSA,L]

When using rewrite rules to add a trailing slash where there is none, a 404 not found error is found instead of a 403.

The rewrite rules have been ok on LSWS for the last couple years for 100 + accounts. The rewrite rules work on all Apache 2.x versions.

I switched to lsws 4.1.12 in the meantime.

Many Thanks!

Quote:

Originally Posted by jp0p (Post 34857)

Hi,

LSWS - Enterprise 4.1.13 on CENTOS 5.8 i686

I tried enabling rewrite logging and nothing showed up in the logs.
...

make sure the followings:

1. LSWS log level (Admin Console => Configuration => Server => Log) set to INFO or DEBUG.
2. "RewriteLogLevel 9" in httpd.conf.

I did both of those before submitting my post: Log level is Info and RewriteLogLevel 9 in httpd.conf.

Pls do force reinstall and see if any difference.

We need debug log with full debug logging enabled in order to analyze what happened.
if you want to have our staff take a look on your server, please contact bug@litespeed... with temp root access to that server.