• Hello,

    am I correct in understanding that the current release of WP Super Cache still does not have a working fix for content being cached “wrong” when accessed with https?

    We need a working solution for separate caching of http and https accesses ASAP! I see something about it being in the “development version” – is there some way I can patch or install a version of WP Super Cache which has this feature?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Yes, it’s still an issue. Please try the development version on the download page. That needs testing, especially with https as I don’t have a https enabled server to test on.

    Thread Starter M?ns Jonasson

    (@mungobbq)

    Thanks Donncha.

    I’m a little hesitant to install a development version on my live server, but I’ll try it out on my dev server first.

    What is keeping this to be implemented in the release version?

    Nobody is testing the development version and giving me feedback on it basically.

    Chances are I’ll revert most of the changes in there and make the next release a bugfix release because a lot of the code is fairly experimental.

    Having said that, it works fine on my own server but when things go live …

    Thread Starter M?ns Jonasson

    (@mungobbq)

    Donncha, I’ve been running the development version live on my production server for a couple of days this week now and I see no problems. The separate caching of http/https works fine, and I have not had any other problems with the plugin.

    I strongly suggest moving the https/http code in to your next release.

    Great, thanks for the feedback ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘https still an issue?’ is closed to new replies.