Not an expert at SSL and HTTPS so jsut had a quick question. Does the use of SSL and a site running HTTPS imply that the communications of all data between the client and server is encypted or does this only mean that the server is authenticated to be the actual server being referenced by the certificate?
It means that the traffic between the client and server are encrypted.
Thanks, that is what I thought but wanted to be sure.
you need to make sure that the certificate has the name of the url you want to secure otherwise the user will be prompted to accept everytime
[QUOTE=Greggers]
you need to make sure that the certificate has the name of the url you want to secure otherwise the user will be prompted to accept everytime
[/QUOTE]
Even with the shared SSL cert? Is the only way to avoid the prompt to have your own URL specific cert?
Shared SSL requires a Wildcard certificate, either on your own domain or by using the .m***here.biz certificate.
If you use the mhere certificate:
You want to secure secure.mydomain.com, you are prompted to create a secure.myhpshere.biz third level alias, people will then access https://secure.mhere.biz (which is an alias of https://secure.mydomain.com ) The certificate will not prompt the user because the certificate secures .m***ehere.biz. If the user accesses https://secure.mydomain.com the user will be prompted (as the certificate does not match)
Hope that makes sense?
PS - I’ve just entered https://www.mydomain.com in my browser and it’s displayed another resellers site???
Edit: When I read back through it didn’t make much sense at all - hopefully it does now.
So with the shared cert you cannot use your own domain then correct otherwise they will be prompted?
I’m pretty sure that is correct - i’m sure someone else will confirm.
I have just had a play with making one of my gash domains secure using a shared SSL and that is the procedure I had o go through (enable Shared SSL through Admin CP - Turn Shared SSL on within Domain CP - prompted to create third level domain alias)
This is correct, unless you are willing to purchase 30+ seperate IPs to setup a seperate shared IP tag for you. Then for each new server you will again have to purchase new IP. Thus not recommeded to go for at the moment.