Cache Busting using htaccess Rewrite rule?

Question

Cache Busting using htaccess Rewrite rule?

Mohamed Omar

2022年3月6日 13:06

I am trying to follow this tutorial that says i can make a server to send a file like style.css if the requested file is style.15458888.css with a rewrite rule to be put inside the htaccess file.

This Rule

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.+).(d+).(js|css)$ $1.$3 [L]

So i followed with this in the head tag:

?php $time = filemtime(get_template_directory() .'/assets/css/main.css');?
link href="?php echo get_template_directory_uri().'/assets/css/main.'.$time.'.css'?" rel="stylesheet" type="text/css"

and this inside the Htaccess:

    # BEGIN WordPress
IfModule mod_expires.c
    ExpiresActive On
    ExpiresByType image/jpg "access plus 6 hours"
    ExpiresByType image/jpeg "access plus 6 hours"
    ExpiresByType image/gif "access plus 6 hours"
    ExpiresByType image/png "access plus 6 hours"
    ExpiresByType text/css "access plus 6 hours"
    ExpiresByType application/pdf "access plus 1 week"
    ExpiresByType text/javascript "access plus 6 hours"
    ExpiresByType text/html "access plus 10 minutes"
    ExpiresByType image/x-icon "access plus 1 year"
    ExpiresDefault "access plus 3 hours"
/IfModule
Header set X-Endurance-Cache-Level "2"
IfModule mod_rewrite.c
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
RewriteRule ^(.+).(d+).(js|css)$ $1.$3 [L]
/IfModule

# END WordPress

As you can see the RewriteRule ^(.+).(d+).(js|css)$ $1.$3 [L] has been added before the /IfModule

And the file name changed correctly having this:

link href="http://ask.prosentra.com/wp-content/themes/tutorialblog/assets/css/main.1504604028.css" rel="stylesheet" type="text/css"

But still the server doesn't implement the rule i mentioned. What is wrong?

Topic rewrite-rules mod-rewrite htaccess cache theme-development Wordpress

Category Web

user24601 · Accepted Answer · 2020年9月25日 21:06

You needed only to add some \'s and reorder your rules to have this before the catch-all rule (have your rule above the WordPress rule).

You want a \ before the periods in this case because you want it to match literal periods in the http request.

You want a \ before the d because we want it to match any digit, not the letter d.

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.+)\.(\d+)\.(js|css)$ $1.$3 [L]

With this we can add any arbitrary digits between the periods in the file name request which will bust cache, but it will remain the same file name on the server.

Mark Kaplun · Accepted Answer · 2017年9月23日 08:13

This is a dead end approch as the enqueue API do not support such versioning format which means that you will have to avoid using it, which is not a great thing. Your specific problem here is that you added the rule too late, RewriteRule . /index.php [L] "transfers" handling to wordpress and nothing is going to be done after that, which means that you need to switch the order of them. And again changing the wordpress core rewrite rules is not smart, you should probably add a specific section outside of the wordpress rules section.

Cache Busting using htaccess Rewrite rule?

About