Originally Posted by iisbum I would do that in two seperate steps. Why not have all traffic for site.com, redirect to www.site.com (better for search engine rankings). You're probably worried here since the SSL certificate is for www.site.com, and not for site.com, but better to redirect all traffic I think. Then in the payment page I would add the https check in the php as someone previously described. You can also do the https check just for that page with rewrite rules, I found this link which should be helpful: http://www.whoopis.com/howtos/apache-rewrite.html Cheers, Mubs

Having the www and no-www shouldn't effect SEO should it? Anyway, I checked out the whoopis.com site and it was helpful as I found out a few things but I followed what they said and I only managed to redirect traffic from http://site.com/payment to http://www.site.com/payment/ (Notice the slashes at the end) It would only redirect traffic without a slash and it still wouldn't move them to the HTTPS.

I think I might have to do some more hunting...

Originally Posted by MaxS I think it will work. Your best bet is to try it. I'm not a mod_rewrite expert.

I tried out your code and it worked the same as the above one. It just put a slash on the end and moved them to the www version. Still no HTTPS no matter how much I change it

Originally Posted by Garrett How? https and http would be 2 different pages right :S

I have seen this on some servers, different folders are setup httpsdocs and httpdocs. Unfortunately my server uses the one file for both versions