Issue with 'Exact URIs to bypass'

  • Resolved zachop

    (@zachop)


    10 years, 2 months ago

    Hi,

    I experience an issue with the exclusion of exact URIs from the cache.

    I’ve been using v2.x of this plugin in WooCommerce installations, so there are certain pages for which the cache has to be bypassed (cart pages etc.).

    Since the upgrade to v3 (currently at v3.1.0) this function doesn’t seem to work.

    I have cleared the whole cache (more than once).

    I have defined the URIs in the form of:
    /cart
    /checkout
    etc.

    I have also tried using the ‘starts with’ URI exclusion mode with the same results.

    The plugin keeps caching the cart page (the response for https://mydomain/cart is 304 – Not modified).

    It might also be useful to know that there’s also WPML running on that site, apart from WooCommerce. The specified URLs are correct, however.

    Is there anything else that I should check;

    Thanks in advance!

    https://www.ads-software.com/plugins/hyper-cache/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Stefano Lissa

    (@satollo)

    Please can you provide a real url so I can test the problem? Have you looked at the page source if there is the hyper cache signature at the end?

    Thread Starter zachop

    (@zachop)

    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.

    Plugin Author Stefano Lissa

    (@satollo)

    Ok, can you send me even a screenshot of the hyper cache configuration? I’m pretty sure it’s ok, but I need some info to try to find the problem in the code.

    Send it at [email protected].

    Thank you, Stefano.

    Thread Starter zachop

    (@zachop)

    I’ve e-mailed you the screenshots.

    Thanks!

    Thread Starter zachop

    (@zachop)

    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!

    Hi zachop, that is great news I am sure many will find your information above handy.

    If you issue is resolved can you mark this support thread as resolved.

    Thank you

    Plugin Author Stefano Lissa

    (@satollo)

    Hi, the end slash issue should be resolved on latest version.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Issue with 'Exact URIs to bypass'’ is closed to new replies.