Hi,
yes in the root directory is wordpress installed so it has [L] tag like this:
Also after that there is a second mention:
Brgds,
yes in the root directory is wordpress installed so it has [L] tag like this:
Code:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
Code:
# END WWW to non-WWW
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]
Last edited by a moderator:
There is a minor difference in the way LiteSpeed Web Server and Apache treat the [L] flag in rewrite rules. The [L] flag (“L” stands for “Last”) causes mod_rewrite to stop processing the rule set. There are two ways to interpret this:
LSWS will try to treat `L` tag similar to Apache in the "future" release, for now you can try using only one [L] in your rule set instead of multiple [L]s.
- In most contexts, including LiteSpeed Web Server, this means that if the rule matches, no further rules will be processed. LSWS exits from the rewrite completely to avoid looping.
- In Apache, [L] means that if the rule matches, no further rules will be processed in the current iteration. Apache does not exit from the rewrite rule completely, and so there is a possibility of looping.
LSWS will try to treat `L` tag similar to Apache in the "future" release, for now you can try using only one [L] in your rule set instead of multiple [L]s.