At 03:25 AM 12/31/99 Fathi Said wrote:
My problem is: I want my clients to think that they are still on my website and don't see the payment.com URL, butstill the ssl.mydomain.com URL in their browsers.
Well....The purpose of a certificate is to authenticate the site. True, we tend to think of certificates as supplying encryption. But if you ask Thawte or Verisign, they'll tell you that the purpose of a certificate is to authenticate the site.
When your visitor's browser gets data from <payment.com>'s secure server, the browser will show the site the data came from. That's why, when you order a certificate, you have to identify the site as it appears in URLs.
You MIGHT be able to go to one of your own pages, and then show <payment.com>'s pages in a frame.
I hope not, though; it would destroy the main point of having security certificates.
Jeff
For non-secure sites this can be done via a Cname (ssl.mydomain.com --> www.payment.com), obviously. But how can I do this forsecure sites so that the browser still indicates "Yes, this site is secure"? Thanks for any help. Fathi