{"id":7684,"date":"2017-07-26T06:00:05","date_gmt":"2017-07-26T10:00:05","guid":{"rendered":"https:\/\/blog.litespeedtech.com\/?p=7684"},"modified":"2017-07-26T06:00:05","modified_gmt":"2017-07-26T10:00:05","slug":"wpw-rewrite-rules-in-the-proper-order","status":"publish","type":"post","link":"https:\/\/lswp.store\/index.php\/2017\/07\/26\/wpw-rewrite-rules-in-the-proper-order\/","title":{"rendered":"WpW: .htaccess and Rewrite Rules"},"content":{"rendered":"

\"\"<\/p>\n

Welcome to another installment of WordPress Wednesday<\/a>!<\/p>\n

We\u2019ve covered a lot of complex topics here lately, so how about we give you a nice quick tip for a change? Today, we\u2019ve got a little tidbit related to your .htaccess<\/code> file and LiteSpeed Cache Rewrite Rules.<\/p>\n

What is .htaccess<\/code>?<\/h2>\n

LiteSpeed Web Server supports the Apache .htaccess<\/code> file. This configuration file is important because it allows us to enable or disable additional functionality, and to define URL redirect rules, among other things.<\/p>\n

When you look at the .htaccess<\/code> in your WordPress root directory, there are two things you should notice:<\/p>\n

    \n
  1. There should be a line that reads CacheLookup on<\/code><\/li>\n
  2. WordPress\u2019 URL rewrite rules (if there are any) should come after<\/i> LiteSpeed\u2019s Cache rules.<\/li>\n<\/ol>\n

    Under normal circumstances, this is not something you should have to worry about. There should not be any need for you to edit this file yourself. LiteSpeed’s WP plugin maintains the\u00a0.htaccess<\/code>\u00a0file automatically. When the plugin is installed or uninstalled, enabled or disabled, or when you change relevant settings in your WP dashboard, .htaccess<\/code> is updated to reflect that change.<\/p>\n

    In some more detail<\/h2>\n

    If you have chosen to use pretty permalinks (i.e. your WordPress URLs look more like example.com\/post-title<\/code> or example.com\/2017\/07\/post-title<\/code> than example.com\/?p=123<\/code>), then WP has used the .htaccess<\/code> file in its root directory to define some rewrite rules. Depending on how many plugins you\u2019ve got installed and a variety of other factors, your .htaccess<\/code> could be fairly simple like the one below, or it could be really hairy with many different blocks belonging to a variety of plugins and other software.<\/p>\n

    WordPress Rewrite Rules<\/h3>\n

    This is an example of the lines that a basic WP installation would insert into .htaccess<\/code>:<\/p>\n

    # BEGIN WordPress\n<IfModule mod_rewrite.c>\nRewriteEngine On\nRewriteBase \/\nRewriteRule ^index\\.php$ - [L]\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule . \/index.php [L]\n<\/IfModule>\n# END WordPress\n<\/pre>\n
    LiteSpeed Cache Rewrite Rules<\/h3>\n
    LiteSpeed Cache, too, uses .htaccess<\/code>. Here\u2019s an example of the LSCache-related lines you might find in your .htaccess<\/code>:<\/p>\n
    # BEGIN LSCACHE\n## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##\n\nRewriteEngine on\nCacheLookup on\nRewriteRule .* - [E=Cache-Control:no-autoflush]\nRewriteRule \\.litespeed_conf\\.dat - [F,L]\n\n### marker CACHE RESOURCE start ###\nRewriteRule wp-content\/.*\/[^\/]*(responsive|css|js|dynamic|loader|fonts)\\.php - [E=cache-control:max-age=3600]\n### marker CACHE RESOURCE end ###\n\n### marker FAVICON start ###\nRewriteRule favicon\\.ico$ - [E=cache-control:max-age=86400]\n### marker FAVICON end ###\n\n### marker WEBP start ###\nRewriteCond %{HTTP_ACCEPT} \"image\/webp\" [or]\nRewriteCond %{HTTP_USER_AGENT} \"Page Speed\"\nRewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]\nRewriteCond %{HTTP_USER_AGENT} iPhone.*Version\/(\\d{2}).*Safari\nRewriteCond %1 >13\nRewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]\n### marker WEBP end ###\n\n### marker DROPQS start ###\nCacheKeyModify -qs:fbclid\nCacheKeyModify -qs:gclid\nCacheKeyModify -qs:utm*\nCacheKeyModify -qs:_ga\n### marker DROPQS end ###\n\n\n## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##\n# END LSCACHE\n<\/pre>\n
    The exact lines you see for WordPress and LSCache depend on which options you have enabled in the plugin, and may not match these examples directly, but they should be pretty similar.<\/p>\n
    Putting Them Together<\/h3>\n
    In order for LSCache to work properly, two things must be true:<\/p>\n
      \n
    1. Public Cache Lookup must be enabled via the CacheLookup on<\/code> directive.<\/li>\n
    2. The LITESPEED WP CACHE PLUGIN<\/code> block must appear before any WordPress rewrite rules.<\/li>\n<\/ol>\n
      If you’re noticing quirky behavior, take a look at your configuration file. You can view it via\u00a0WP Dashboard > LiteSpeed Cache > Toolbox > View .htaccess<\/strong>.\u00a0Like we mentioned earlier, LSCache for WordPress automatically handles cache-related changes to .htaccess<\/code>, but if it has been manually updated or otherwise manipulated by another plugin, you may find irregularities that need to be corrected.<\/p>\n
      —<\/p>\n
      Have some of your own ideas for future WordPress Wednesday<\/a> topics? Leave us a comment!<\/p>\n
      Don\u2019t forget to meet us back here next week for the next installment. In the meantime, here are a few other things you can do:<\/p>\n