Cache Vary, custom rules in .htaccess and unsing Crawler with cache vary

you need to add this OUTSIDE of LSCWP marker in your .htaccess file

you can use cookie simulation in crawler setting.

Putting this rule outside of its tag leads only to not working website, as all WordPress data in .htaccess is destroyed.

More than that, as I read before, there was an instruction to use this string INSIDE this module.

So putting LS specific rule outside of IfModule LiteSpeed tag ends bed.

<IfModule LiteSpeed>
RewriteEngine on
CacheLookup on
RewriteRule .* - [E=Cache-Control:no-autoflush]
RewriteRule .? - [E=Cache-Vary:city]
RewriteRule .litespeed_conf.dat - [F,L]

no , if you put it into of this block , it will be overridden when you save plugin’s setting

please show me the full content of htaccess where it goes “bad”

404 error on every website page sound’s not “bad” enough?

“no , if you put it into of this block , it will be overridden when you save plugin’s setting” – yes, I know, that’s why I opened this topic, to get safe method of keeping this rule inside. And when this string is putted outside all wordpress rules get wiped on enabling / disabling debug mode.

So the question is, where exactly this string should be put if there is no other option to ensure safe keeping this string into LS configuration?

yes, that’s why I asked you to show me the content of htaccess when it goes bad so I can review it

I have bunch of sites and I just add additional directives like that

Ok.

Case #1. Rule added to WordPress section:

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
RewriteRule .? - [E=Cache-Vary:city]
</IfModule>

# END WordPress

Result – rule not applied.

Case #2. Rule added to end of file:

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

RewriteRule .? - [E=Cache-Vary:city]

Result – rule not applied.

Case #3. Rule putted right after LS closing comment:

## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##

RewriteRule .? - [E=Cache-Vary:city]

Result – rule applied, pages cached separately based on given cookie value, no 404 errors on pages.

Right placement of custom rule – after closing LS comment:

## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##

RewriteRule .? - [E=Cache-Vary:city]

Result – rule applied, pages cached separately based on given cookie value, no 404 errors on pages.

These 2 no applies, because you put it at bottom, after a L flag, where L as Last, so any rule below will not be processed

I an more wondering the 404 case, and please share me the full content of it

you should place it before the first LSCWP marker, or after bottom marker but before WordPress rules

“I an more wondering the 404 case, and please share me the full content of it” – I did not catсh same bug while testing on stage environment so I doubt it will help you at this stage.

Thanks for your help, issue resolved.