When moving from a secure page to a page listed to not use secure pages and the option Switch back to http pages when there are no matches is set it works perfectly.

But if you have boost enabled for the http page when the user clicks the link, the cached page is loaded up through the secure url.

Ultimately not a huge problem as it doesn't break the site, but not going through to http. I assume this is because boost is called before securepages.

Comments

kambui’s picture

kambui commented
Issue tags: +boost, +SecurePages

Any fix for this ?

We are having the same issue

kambui’s picture

kambui commented
Version: 5.x-1.7-beta1 » 6.x-1.8
Priority: Normal » Critical

This is a critical issue for us, using boost 6.x-1.0

vacilando’s picture

vacilando commented

Same problem.

Anonymous’s picture

Anonymous (not verified) commented

I'll investigate this problem over the weekend

Lloyd’s picture

Lloyd commented

Any update on this? I'm having the same issue.

jaybee1001’s picture

jaybee1001 commented

Hi - has there been any progress to identify the cause of this issue?

Many Thanks

JB

mkeplinger’s picture

mkeplinger commented

Any status on this? I think that all that needs to be done is to change the default "weight" of the module to be less than Boost's weight. Currently the weight of boost is -90.

You can also temporarily set this by using the module weights module and setting the "weight" of the Secure Pages module to be -91
using the Util Module: http://drupal.org/project/util

If I knew how to make a patch I would. But basically, this can be fixed by modifying the weight of the module. SEE: http://drupal.org/node/110238

jm.federico’s picture

jm.federico commented
Version: 6.x-1.8 » 6.x-1.x-dev

This is not a Drupal problem, is an .htaccess config problem

Boost serves the pages from a static cache, Drupal doesn't get called. If you want the page to be served using http, you have to create a redirect rule on your .htaccess file

Changing the weight on the modules will have no effect, as I mentioned, Drupal doesn't get called. Apache (or whatever server you use) is serving the page directly.

This issue should be moved to the BOOST queue. (Leaving here, will leave up to the Developers to decide)

mikeytown2’s picture

mikeytown2 commented

dev version of boost will not try to serve the page from the cache if protocol is https. This is a htaccess issue.

patrickroma’s picture

patrickroma commented

Any News on this issue?

grendzy’s picture

grendzy commented
Status: Active » Closed (duplicate)

I don't think this can be fixed by securepages, because the current folder structure of boost doesn't include the protocol in the cache key. Example:
cache/normal/example.com/_.html

I'm closing this as a duplicate, because a new folder structure has been proposed that would account for the protocol.
#1070048: New folder structure