A subset of our web pages require HTTPS. These are pages like login, account information, user information, order creation, etc.
On our original web-pages at KaDonk, we have a special plug-in module that automatically switched back and forth between HTTPS and HTTP. All we have to do is move a page to a sub-folder, and -pif- it's HTTPS. Everything is automatic. Love it !
Let's see if I can get the same spiffy functionality with umbraco:
1. After much searching, both in the forums, and in my soul, it seems there is no easy way to implement HTTPS, except by writing a little script that could be placed in a template on each page. This is, by the way, similar to what google does for their urchin scripts, to avoid having 'unsecure components' on a page when using IE.
Suggestion to umbraco: Implement a flag or a rule that can enforce HTTP or HTTPS, or 'retain' for each page. Doesn't matter how it's done, but this is a very basic feature that could easily be 'built in'.
The problem with a script on each page is that it complicates things, adds to downloads (not much, but), and just seems clumsy. Less scripts = good.
2. I can't get myself to do the script, so instead I will attempt to move over my old SecureWebPageModule. Hey, someone did already, but I have to change the code to get it to work with umbraco.
So, back in Visual Studio, make the change the article suggest, compile, deploy, and...? Yeah, it works, even with my virtual folders!
Three full days into this, digging through articles like crazy and every little thing takes hours to learn or figure out. It seems clear that umbraco is not for the faint of heart...! I'm considering my options at this point, is it really worth it??