Title: HTTPS will not forward to HTTP on non-secure pages, when Super Cache is active
Last modified: August 21, 2016

---

# HTTPS will not forward to HTTP on non-secure pages, when Super Cache is active

 *  [wboykin](https://wordpress.org/support/users/wboykin/)
 * (@wboykin)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/https-will-not-forward-to-http-on-non-secure-pages-when-super-cache-is-active/)
 * WordPress HTTPS (SSL) Version 3.3.6
    Conflict with WP Super Cache Version 1.3.2
 * The HTTPS plugin is set to redirect users to HTTP if a page is not secure, but
   this does not work after Super Cache starts caching pages. Is this a known problem?
   It appears that the caching is bypassing the secure rewrite rules.
 * [http://wordpress.org/extend/plugins/wp-super-cache/](http://wordpress.org/extend/plugins/wp-super-cache/)

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

 *  [cdanni](https://wordpress.org/support/users/cdanni/)
 * (@cdanni)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/https-will-not-forward-to-http-on-non-secure-pages-when-super-cache-is-active/#post-3712185)
 * Following up on wboykin’s post (we work together):
 * The site in question had options set in HTTPS for domain mapping for sharethis.
   com and gravatar.com.
 * We have another site that uses both plugins, same versions, same WP core (3.5.1)
   and it redirects to HTTP on non-secured pages just fine. The only difference 
   is that it doesn’t have anything listed for domain mapping.
 * At this point we aren’t sure which plugin is causing the issue, so I’m going 
   to follow up in the other plugin’s support forum as well.
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/https-will-not-forward-to-http-on-non-secure-pages-when-super-cache-is-active/#post-3712193)
 * I’ve never used “WordPress HTTPS” so I can’t comment on that. I would say you
   should debug that plugin, adding error_log statements to find out how it works.
   I presume it’s a relatively small plugin so shouldn’t take long, especially if
   the problem is consistent.

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

The topic ‘HTTPS will not forward to HTTP on non-secure pages, when Super Cache 
is active’ is closed to new replies.

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [HTTPS](https://wordpress.org/support/topic-tag/https/)

 * 2 replies
 * 3 participants
 * Last reply from: [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * Last activity: [13 years, 1 month ago](https://wordpress.org/support/topic/https-will-not-forward-to-http-on-non-secure-pages-when-super-cache-is-active/#post-3712193)
 * Status: not resolved