How to control https for special pages

On a seminars site, I want to use SSL on the registration forms only. So I installed revoSSL and did as said in the documentation: created a TV makeSSL, set it to "Yes", and assigned it to the registration template. My first tests were positive, nice switch between http and https pages. But now, one day later - could not figure out exactly what happened in between - the whole site serves as https. This is not what I wanted, I cannot make sure that no mixed content warnings will come up. So I would be glad to fix this.

What may have happened? - I had been playing with this tip from opengeek, Bob Ray and others: call site_url uncached.

Can't say if this was the reason, or if it had been so before - from that point on I realised the site is https. How can I fix it? I tried to clear MODX cache, clear browser history, call the site by http - it always switches back to https.

Is it Google who tries to force https? Anyway, I don’t want it.

Hope someone can comment on this issue.

Best,
Brigitte
[ed. note: BrigitteB last edited this post 9 years, 2 months ago.]

Hi

I can't comment on an answer to your question specifically but I would like to question why you wouldn't want to serve a secure site to your users if you have an ssl already? Removing protocols from external requests should sort out the mixed content issue and you'll have a secure site with seo and pet technique benefits.

Removing protocols from external requests - I was not aware that it would be so easy. Are you sure? I will try it out.

Anyway, it is something to scan for through hundreds of already existing ressources, and to teach the editors how to do it. I would prefer it would work without that.

From the security point of view, I cannot see much gain in an encrypted content page. Or waht do you think?

Brigitte

Browsers will typically continue to connect with the same protocol as the previous page when on the same domain name.
The only way to change that would be to set up specific rules in your .htaccess file or similar.

Honestly though, these days it's better to serve everything via https. Google will even rank you better for it.

+1 for making the whole site https.

Both Google and Firefox are pushing this so your pages will look out-of-date without the little secure lock symbol in the address line. They will be secure enough, but naive users won't think so.

Using https for the whole site used to slow things down, but that's no longer the case, and in many situations, https is now faster. With http, the browsers take time to check for user input on every page so they can issue a warning.