Hi.

I'm using SecurePages to force only one page in site to be SSL protected - the rest should be HTTP, hence I have the "Force redirect to HTTP".

Problem is, that after any page refresh, the SSL becomes active, and there is no re-direct back to HTTP.

Is this a known issue, and is there any way to solve it?

Thanks.

Comments

SyRenity’s picture

SyRenity commented

I mean that the HTTP page is available only once.

After every subsequent refresh, the page is loaded over HTTPS.

Anonymous’s picture

Anonymous (not verified) commented

If the page you're refreshing has a path alias (i.e., node/123 -> some/fancy/path), you can workaround this bug by adding both the alias and the internal path to the Secure Pages configuration (i.e., both node/123 and some/fancy/path should be listed).

I'm not sure what causes this, but it may be something related to some of the other reported problems using aliases.

YK85’s picture

YK85 commented

subscribing

Anonymous’s picture

Anonymous (not verified) commented

Interesting , ill investigate tomorrow

Best,
Paul Booker
Appcoast

adr_p’s picture

adr_p commented
Status: Active » Needs review

Please see http://drupal.org/node/587000#comment-4519010.

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Needs review » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks