vB seo + litespeed cache

[NiteWave]

you are right.

Not only that rule, but also all other rewrite rules, leave them "as is", without change. for complex rewrite rules, it's very tricky and risky to change anything.

[ihstiv]

Ok - thanks. I'll make the necessary changes.

two more questions:

1. can you help me understand this line:
#RewriteCond %{ORG_REQ_URI} ^/(index\.php|)$

..and why it is commented out?

2. is there a way to use the 'private cache' feature in lsws for vbulletin/vbseo logged in members?

[NiteWave]

1.please remove it:
#RewriteCond %{ORG_REQ_URI} ^/(index\.php|)$
it's for test purpose: enable cache for homepage only.
if test pass, comment it out.

2.we've no chance to test "private cache" with vB/vbseo yet.

[ihstiv]

Originally Posted by NiteWave

usually there exists such a rewriterule in .htaccess of document root:

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:

#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

[freeballt]

Originally Posted by ihstiv

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

I'm wondering the same thing.

I also tested this on 3.8.4 and it doesn't seem to execute this: "header('X-LiteSpeed-Cache-Control: no-cache');"

Many of my users are complaining about being logged out, and when I look at it in firebug it doesn't seem to have no-cache in response.

I also had to disable the plugin because if a user is IP banned, it will show an IP banned message to other users.

[NiteWave]

Many of my users are complaining about being logged out, and when I look at it in firebug it doesn't seem to have no-cache in response.

this header "X-LiteSpeed-Cache-Control: no-cache" is used between litespeed processs and lsphp5 process, will not show in response header, so not seen by firebug

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.

can you test homepage only(as discussed before), or another page, the rule is like:
RewriteCond %{ORG_REQ_URI} ^/test-this-page/)$
and clear cache folder first. only after succeeded for 1 page, then move on.

[jdeg]

Originally Posted by ihstiv

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.

I'm having the same issue - if I move the rules to the bottom nothing gets cached though.

Has anyone figured this out?

[NiteWave]

moving the rules to top is recommended. if not working, you can post your rules here to see if any change to improve them.

[jdeg]

I was using your rewrite rules from the first post right after the
RewriteCond %{HTTP_HOST} !^site\.net
RewriteRule (.*) http://site.net/$1 [L,R=301]

[jdeg]

I wonder if this has something to do with gzip being enabled?