Switching between boost cached pages and SSL pages

It does not seem to be possible to switch to a non SSL page form a SSL page when the non SSL page has been cached by boost.

Here is an overview of my issue:
Some of the pages such as e-commerce related pages and user edit pages in my website require https. The menu links in the primary and footer have pages which are static and needs to be cached using boost, and so I have enabled boost for these pages.
Now when the menu links linking to the boost cached pages are clicked in the https page, the switch from https to http does not happen (which happens when boost is disabled). Some resources like some CSS and JS files do not load for the https versions of these static pages.

Proposed resolution

I unsuccessfully tried writing rewrite rules in .htaccess

Please recommend other solution which I could try.

Comments

Anonymous’s picture

Anonymous (not verified) commented
Priority: Major » Normal

Are the links in the menus http links ? It's quite likely that once inside of https Drupal would remain there. Are the links to the javascript and not loading css in the https pages correct ? Some browsers will not mix https and non-https files because of hijacking.

Possibly the best solution would be to look at one of the other caching mechanisms available. Boost disables entirely for https to avoid caching private information. Therefore boost is not really recommended for a site where there is a mixture of pages, as cookies are not transferable between https and http for domains so log in information can get lost as boost would not be able to recognise that someone had for example added some purchases to a cart on a https session.

giorgio79’s picture

giorgio79 commented

Possibly related #1466480: Caches URLs as HTTPS leads to issues when accessing by HTTP

sudev.pradhan’s picture

sudev.pradhan commented

Thanks Philip for the quick response!
I guess you are right, so I am looking at other caching mechanisms like authcache with core drupal caching. Also memcache is already installed and running. If you can suggest any other caching which would be useful in my scenario please do so.
Thanks again,
Sudev

Anonymous’s picture

Anonymous (not verified) commented

authcache with core drupal caching

is at least designed for your scenario a lot more than boost. You may be able to use boost with static pages like "about us" etc, and use the "cache only these pages" functions in boost which would reduce load caused by spiders viewing the site not through https. Boost could even work with a set of very complex rewrite rules which would need to fit into the general design of the shop, so for example a product page could be cached but ono if it had no need for logged in content (which unfortunately means the omission of shopping cart info on a page unless stored in an ajaxed frame or like pricing discounts.

For example on a shopping cart page where Drupal is going to have all the links to the products as https, a set of rewrite rules could redirect back to the http side of the site and boost cached items.

The main reason for keeping boost would be for search engine ranking and spidered page delivery, although "the public" would rarely see the cache, google does rank on page speed delivery and serving static pages to the search engines does have the benefit of keeping the CPU cycles for the customers.

sudev.pradhan’s picture

sudev.pradhan commented
Issue summary: View changes
Status: Active » Closed (fixed)
sudev.pradhan’s picture

sudev.pradhan commented
Status: Closed (fixed) » Closed (won't fix)