• Resolved John Huebner

    (@hube2)


    I need to not cache pages if there is a specific query parameter in the URL. I did a search and I found a similar topic that mentions

    “WP Super Cache settings—particularly the section on rejecting or accepting URLs with query parameters.”

    I cannot find any settings for this in the settings. What am I missing?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @hube2,

    Hi there,

    To exclude pages with specific query parameters from being cached, follow these steps:

    1. Navigate to?Settings → WP Super Cache?in your WP Admin.
    2. Go to the?Advanced?tab.
    3. Scroll down to the?Accepted Filenames & Rejected URIs?section.
    4. In the?Rejected URL Strings?field, enter the query parameter you want to exclude. For example, if you want to exclude URLs with??nocache=true, you would enter?nocache=true.

    You can find more here: https://jetpack.com/support/wp-super-cache/

    I hope this helps, but if you have any questions, please let us know.

    Thank you!

    Thread Starter John Huebner

    (@hube2)

    In my case I have a client that has a single sign on through a third party. The process is that clicking on the login link takes you off site to the sign on and then returns to the site with a single sign on token. This uses the query parameter of “sso”. There may also be other values before or after the sso token. Would it be sufficient to block “sso=”

    Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hey @hube2 – In the Rejected URL Strings?field, could you please add .&.sso=.* and check if this helps? Before checking, make sure to clear existing cache after adding it.

    Looking forward to your reply!

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hey @hube2,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter John Huebner

    (@hube2)

    I’m good, I have not implemented yet but I think I’ll be able to figure something out. At first I was expecting a setting specific to URL query values but as it’s done be blocking parts of the full requested URL that includes the query string I can understand what I need to do.

    Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hello @hube2 – That makes sense! It’s good to hear you’re feeling confident about figuring it out. If you run into any issues or need further clarification, feel free to reach out. We’re happy to assist!

    For now, we are marking this as resolved!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.