papillon
06-23-2002, 11:02 PM
hi,
I ordered a quickssl cert from geotrust for secure.domain.com, After receiving my webhost installed it for me. Now my question is ..
Is it so that since the cert is for secure.domain.com I can only access the 'secure' subdomain using https:// ? In other words, I THOUGHT that once it is installed I could only access files which are stored in my 'secure' subdomain ..and nothing else on my website.
However, once installed this is what effect the cert has:
https://secure.domain.com is pointing right to my front page (not anything stored in the 'secure' subdomain)
And as such I can access the whole website through https://secure.domain.com ...which is cool n all, but is it meant to be like this?
And also, for some reason the 'secure' subdomain disappears from cpanel, and it isnt even counted as a subdomain .. if I try to add a new subdomain 'secure' it says one already exists ..and indeed I can access http://secure.domain.com (not secure) ..it takes me to my front page (unsecure)
Is this all normal behaviour of an SSL cert? What I thought would happen was that since I ordered the cert for secure.domain.com I would HAVE TO store all files I want secure in my 'secure' subdomain ...
papillon
I ordered a quickssl cert from geotrust for secure.domain.com, After receiving my webhost installed it for me. Now my question is ..
Is it so that since the cert is for secure.domain.com I can only access the 'secure' subdomain using https:// ? In other words, I THOUGHT that once it is installed I could only access files which are stored in my 'secure' subdomain ..and nothing else on my website.
However, once installed this is what effect the cert has:
https://secure.domain.com is pointing right to my front page (not anything stored in the 'secure' subdomain)
And as such I can access the whole website through https://secure.domain.com ...which is cool n all, but is it meant to be like this?
And also, for some reason the 'secure' subdomain disappears from cpanel, and it isnt even counted as a subdomain .. if I try to add a new subdomain 'secure' it says one already exists ..and indeed I can access http://secure.domain.com (not secure) ..it takes me to my front page (unsecure)
Is this all normal behaviour of an SSL cert? What I thought would happen was that since I ordered the cert for secure.domain.com I would HAVE TO store all files I want secure in my 'secure' subdomain ...
papillon
