Replies: 0
We are using WP 4.7.2 with woocomerce and w3 total cache 0.9.5.2 on nginx – all configuration is inline with the codex (https://codex.wordpress.org/Nginx),
We have a situation where a single permalink for a subsection is returning a 404 error directly from nginx – other permalinks in the same category are being processed properly, and creating a random URI under the category returns to WP 404 page.
For example a valid resource permalink “https://<domain>/store/pdf-resources/resource-1” returns the page it’s supposed to. A random resource “https://<domain>/store/pdf-resources/resource-foo” returns the WP instances pretty 404 page. One single permalink (out of some 250+) “https://<domain>/store/pdf-resources/resource-estevanico” returns the nginx 404.
Extensive debugging of the the rewrite rules and nginx config shows that (as configured) resources in this class are not to be cached by W3TC – it matches the rule to set the “null cache”, and a negative match for logged in users and /wp-admin access (which even if it matched would set “null cache”). The very next line in the nginx log is an open() on /<webroot>/store/pdf-resources/resource-estevanico – which seems odd to say they least.
This particular resource has been re-created from scratch more than once, each time with a different permalink, each time with the same result.
Can anyone shed light on why one single resource like this is not being addressed properly?
Is there a way to get WP to show it has received the request?