Small problem with this whole idea.
Everything in the page source also needs to be called using a ssl (443/HTTPS) connection. Any images, css, javascripts, everything being displayed or it isn't an encrypted connection. This is a common issue in most content management systems today.
Go download and use
Google Chrome. It'll show you strait up if everything being displayed is encrypted. If everything in the page is not encrypted, chrome turns the HTTPS in the address bar red and but a line through it. If everything in the page is encrypted then chrome will show a green HTTPS in the address bar.
Firefox does not tell you if everything being displayed is encrypted or not. All firefox does is shows you the HTTPS in the address bar.
I don't use internet explorer and haven't in many years so I have no idea if IE warns you or not.
I suggest you go download
Abyss Web Server: Mod Rewrite Translator. It is the greatest tool ever for translating htaccess to Abyss' URL Rewriting.
Clicking this thumbnail image will shows you how to setup abyss to redirect to an encrypted connection. Doing this will shorten the load time of your pages from what was explained in the post above mine.