zachop

@danieliser you’re right. I got involved with troubleshooting that setting after an unsupported value had already been stored, so I didn’t get a chance to read the placeholder.

Thanks for your time!

Hi,

I’ve managed to identify the exact cause of the plugin’s behavior, so I’m following up here for future reference.

If a URI ends in a slash (e.g. https://www.mydomain.com/cart/), then the plugin doesn’t consider that URI to be an exact match with ‘/cart’ (without the slash).

However the new “starting with” exclusion mode does catch that case and excludes the page from caching.

The reason why I mentioned that “starting with” mode didn’t seem to work, in my first post, is that I had probably forgotten to empty the cache in between the attempts.

If a page gets cached (not having been excluded), then the cached version is served by the plugin, even if the URI is thereafter added to the exclusion list. One must empty the cache each time the bypass rules change.

Stefano thanks for your time, effort, and immediate response!

I’ve e-mailed you the screenshots.

Thanks!

Sure, you can have a look at https://dev.eco-buy.gr

The bypass for exact URIs is enabled there, and /cart is included in the URIs.

However, hyper cache seems to interfere. If you add a new product to the cart, you get its old contents until you refresh using Ctrl+F5.

Yes, there’s a hyper-cache signature at the page source.

I can also provide screenshots of the plugin’s settings and the response headers.