| 1 |
Zhang Weiwu wrote: |
| 2 |
> Sorry about the badly named and impolite email subject line. I thought I |
| 3 |
> was composing to my friend. |
| 4 |
|
| 5 |
If this is for a dns or layer4 load balancer, you only need one SSL, as |
| 6 |
long as the URL in the task bar remains "www.domain.com", it doesn't |
| 7 |
matter which IP/box it goes to. |
| 8 |
|
| 9 |
Your other option is to look at other cert's.. |
| 10 |
|
| 11 |
We're using Thawte as it's still a recognized brand. For us it's not |
| 12 |
just the "oh.. the lock is turned on at the bottom". It's about, "oh, |
| 13 |
this site has been confirmed by $TRUSTED_CA." Still, thawte is tons |
| 14 |
cheaper than verisign.. even through they are divisions of the same |
| 15 |
company. go figure. |
| 16 |
|
| 17 |
Another option you have is to register one cert, and redirect all your |
| 18 |
https requests to subdirectories of the secure server. Like this: |
| 19 |
|
| 20 |
http://www2.domain.com/signup.html |
| 21 |
form action is -> https://secure.domain.com/www2/signup.cgi |
| 22 |
|
| 23 |
http://www5.domain.com/shopping/site.html |
| 24 |
cart URL is -> https://secure.domain.com/www5/cart.cgi |
| 25 |
|
| 26 |
as long as you have a database where you can store state information, |
| 27 |
you can bounce the user from one server to another and back. |
Archives