[Plugin: WP Super Cache] HTTP HTTPS Caching

  • Scott Kingsley Clark

    (@sc0ttkclark)


    15 years, 8 months ago

    How does WP Super Cache handle a site that is running HTTP for users not logged in, and HTTPS for users logged in? The site’s got ecommerce functionality available only for logged in users.

    It appears that when an admin updates pages or content, the cache isn’t updated on the http version of the page. Is this correct or am I looking at another issue? I’ll keep investigating, just putting this here for the trail in case someone else has the same issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    15 years, 8 months ago

    Unfortunately the protocol isn’t saved for supercache users. Try “half on” mode. That should work better for you.

    Thread Starter Scott Kingsley Clark

    (@sc0ttkclark)

    15 years, 7 months ago

    The site is in half-on mode right now, it looks like it’s saving the URLs in the key saved in the meta file is:

    url-to-pagewww.thewebsitehere.com443/url-to-page/here/

    Could this be what’s being checked against during loading via cache? If so, even with the ‘Clear cache on save’ option set, the cache remains (the admin edits on https and non-logged in users usually see http by default.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘[Plugin: WP Super Cache] HTTP HTTPS Caching’ is closed to new replies.