We are going to start using Sites to capture some personal details, so this will facilitate using SSL in the form. We will want to use a custom domain name to mask the force.com site (eg. subscribe.ourdomain.com instead of site.secure.force.com)

I know that force.com has its own SSL certificate for *.force.com, however my concern is that if we override with a custom domain name, the browser will see an inconsistency between the URL (ourdomain.com) and the SSL certificate for force.com, and display an ugly 'exception' page (which most browsers now do - IE7/8, FF3).

Is there any way to get round this? Will this even be an issue with custom domain names? We are not in live yet so I can't properly test this case, however would be interested to get some feedback from the SFDC sites product team on this... :)

Thanks

Stephen