It is true that you can only apply a secure certificate to a single subdomain, or if you pay more for a “wildcard” certificate, to the entire domain (and any and all subdomains within it). Apache servers can be configured to listen on both ports 80 and 443, and to point both of those virtual servers at the same document root. What becomes incredibly chancy is getting Apache to only accept connections to a single page over port 443 rather than 80. You could probably more easily set up a redirect in a folder, so your contact form might be placed at https://example.com/contact/[index.html] rather than https://example.com/contact.html.
Setting both the secure server and the Apache redirects is not a trivial thing. For one matter, many shared hosting setups will require you to have two separate root folders, which would mean that you would need to maintain two different copies of your site on your server. For another, you will need to make your links into and out of the secure area using “External” URLs in Freeway, rather than the usual automatic page links. This means you will have to type in https://example.com/whatever/ in the Hyperlink dialog, rather than just choosing a page to link to from the popup list.
Modern servers and browsers are very fast at encryption/decryption these days, though, so you might just do what I usually do when I need security, and make the whole site secure. That’s actually a whole lot easier than trying to switch back and forth.
Walter
On Dec 20, 2012, at 8:20 AM, Marco wrote:
I’d like to have my contact pages (where visitors submit data to me) to be on a secure page (so with SSL). I’ve looked into SSL and I should be able to by a SSL certificate for my domain. My question is how I am going to make my contact page secure while other pages are just regular pages.
I’ve seen websites that use http://www.companyname.com/whatever.html while their contact page is https://www.companyname.com/contact.html.
On this forum I’ve read that you can only get an SSL certificate for your whole domain. How does this work exactly? Can I use both http and https pages (which I prefer because of speed)? And does this mean that I’ll have to set up a different Freeway document for the secure pages (and files)?
Any help is appreciated!
Regards,
Marco
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options