View Single Post
  #14  
Old 07-15-2011, 01:28 PM
ihstiv ihstiv is offline
New Member
 
Join Date: Jul 2011
Posts: 6
Quote:
Originally Posted by NiteWave View Post
usually there exists such a rewriterule in .htaccess of document root:
Code:
RewriteCond %{HTTP_HOST} !^www\.mysite\.org$
RewriteRule ^(.*)$ http://www.mysite.org/$1 [R=301,L]
just insert the new cache related rules after above rules:
Code:
#rules for litespeed cache:
RewriteCond %{HTTP_COOKIE} !vbseo_loggedin=yes
RewriteCond %{HTTP_COOKIE} !bb_userid=
RewriteCond %{HTTP_COOKIE} !bb_password=
#RewriteCond %{ORG_REQ_URI} ^/(index\.php|)$
RewriteCond %{REQUEST_METHOD} ^HEAD|GET$
RewriteCond %{QUERY_STRING} ^$
RewriteRule (.*) - [E=Cache-Control:max-age=60]
[/CODE]
I've found that moving the lsws rules to the top of the htaccess file tends to cause problems, including 404 errors. The only thing that solves the errors is to move the lsws rules below all existing VBSEO RewriteCond and RewriteRule statements.

RedirectMatch and other statements can go below it w/o problem.

Knowing this, does it still make sense to leave this line as-is:
RewriteRule ^(.+)$ vbseo.php [L,QSA]

..or would it be better to change it to this?
RewriteRule ^(.+)$ vbseo.php [QSA]

Cheers
Reply With Quote