Can this be done without using a subdomain?
I am very new to this, want to get my shop secure and up and running. I'm pretty confused about the whole affair.
Can this be done without using a subdomain?
I am very new to this, want to get my shop secure and up and running. I'm pretty confused about the whole affair.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
OK, without wishing to confuse you any further, you DO realise that "www." is actually a subdomain itself, don't you?
I see a LOT of posts in these forums from people that actually *WANT* to use the 'www.' subdomain rather than the just the domain name itself.
Anyway, I see the Dr. has provided you with a link on installing an configuring SSL, and those instructions remain the same regardless.
The *important* thing for *you* to consider is What URL do you want your users to see/use when accessing the SSL portion(s) of your site?
In ALL cases the URL will start with "https://" but what follows could be almost anything, eg.
"https://mycomputer/" (intranet only)
"https://mycomputer.mydomain" (intranet only)
"https://mycomputer.mydomain.com"
"https://www.mycomputer.mydomain.com"
"https://www.mydomain.com"
"https://mydomain.com"
All of these are variants are valid/possible (to whoever owns the 'mydomain.com" domain name), but you *must* decide on the name *before* you purchase you SSL cert (unless you are really rich and purchase a 'wildcard' certificate).
If you purchase your SSL certificate for "www.mydomain.com" it won't work if you direct your customers to https://mydomain.com", likewise a certificate purchased for mydomain.com won't work if you direct your customers to "https://www.mydomain.com"
Hopefully you'll find this info useful
Cheers
Rod