mattwthomas

I guess I’ll just do the filters at the end here: https://developer.jetpack.com/docs/customization/wp-super-cache/wp-super-cache-developer-documentation/

If there’s a variable, let me know. I think a variable would be preferable.

I am aware that most of the other rules correspond to these options. I did but mean to offend you and I did not use the word “useless”. I just said that these options are unnecessary — which you point out in the interface for the plugin. If you need them, it’s because you’ve done something unusual.

On the sitemap and robots files, these rules only work if these are static files because the try_files directive is not inherited. As a result, these rules actually prevent those files from being accessible if they are generated by PHP. As a result, this breaks vanilla WordPress! This is true no matter how you configure nginx (though it’s possible to use a named block to work around it).

The static block does something similar in that it will block PHP from generating any file with any of those extensions. I don’t know of a case where it matters, but it could break something. A similar result can be achieved by putting a rule in /. This is probably what most people want.

Last comes the header override. As you know, this is only useful if you have a conflicting plugin. This is the one that requires a non-default nginx module to clear the headers. So, it’s the source of this confusion. I don’t have any reason to think that @fidoboy needs this.

I really appreciate this extension and think that you’ve done great work on this. I still stand by my post though. Those are the two magic lines for nginx. It will work on any vanilla setup with just those.

These lines belong in your server block. The file that you want is probably in /usr/local/nginx/conf/conf.d/.

I use nginx. Thanks @isaumya for maintaining this plugin. Honestly, all you need is

location /wp-cron.php { add_header Cache-Control "no-cache, no-store, must-revalidate, max-age=0"; expires -1; }
location = /wp-content/wp-cloudflare-super-page-cache/chriskthomas.com/debug.log { access_log off; deny all; }

Everything else is completely unnecessary. It all works out of the box. Most of the other lines actually reduce functionality in nginx.

Static cache rules should be set using the main / block. Dynamic cache rules are set dynamically using this plugin. There’s no need to override them in nginx.

• This reply was modified 2 years, 6 months ago by mattwthomas.
• This reply was modified 2 years, 6 months ago by mattwthomas.
• This reply was modified 2 years, 6 months ago by mattwthomas.