Yep, although you might want to make sure and wait for someone else here to confirm this as I am on the fence. Better yet, why don't you e-mail the iPage guys because they can help better...
Please, bumping is not allowed..
With it going to store versus catalog that is a setting in your configure.php file. most sites with the ssl installed properly and the os setup properly, can use the same directory structure for ssl and non-ssl.
You are limiting yourself if you get your ssl at.
You are just assigning an ssl to the subdomain. you can get a cert which will do that, and any other subdomains you want, as well as the main domain..
But I could post the same question again, no?.
I don't understand the argument for/against putting the SSL on the whole domain. I just heard suggestions to separate them. And many sites I've been to do the same..
I have 'www.mydomain.com' as well as 'forums.mydomain.com' and 'store.mydomain.com'. If I were to put an SSL on 'store.mydomain.com' it limits me somewhat I'd have to use that subdomain for SSL email, for example. Having 'secure.mydomain.com' allows all the SSL traffic to go to that subdomain..
Most importantly, is it -possible- to put the SSL on a separate subdomain? I can't seem to get it working properly, but -only- at this one spot (Sign In from the login.php page)..
If your iPage domain is e.g. www.yourdomain.com then that is what your ssl certificate should be issued to. The reason you have problems is because of the way you have set your store up..
If the SSL server is on a physically different machine then you need to define that you store the session id's in the database. Otherwise the switch between https will keep loosing the session id..
This setting is in the configure.php file.
Canni remeber the setting off hand..
Some one else will know for sure,.
Vger- My store is on a different subdomain (store.mydomain.com), so having an SSL cert issued to www.mydomain.com will not work, as per my understanding..
Willows- The store isn't on a physically different machine. And, for the most part, switching from http to https works just fine. The -only- place I've noticed problems is the initial login screen when you click "Sign In"...
I currently have a store setup at.
And am going to get a security cert for this site. However, to separate things, I'd like the cert for.
Now, under my 'secure.mydomain.com' path on the server, I have a link called "store" that points me to "store.mydomain.com/catalog".
My understanding is that I set things up as follows:.
ENABLE_SSL = true.
HTTP_COOKIE_DOMAIN = store.mydomain.com.
HTTPS_COOKIE_DOMAIN = secure.mydomain.com.
HTTP_COOKIE_PATH = /catalog/.
HTTPS_COOKIE_PATH = /store/catalog/.
DIR_WS_HTTP_CATALOG = /catalog/.
DIR_WS_HTTPS_CATALOG = /store/catalog/.
This works a little bit. When I click "log in", it correctly routes me to the login page on.
However, when I enter the information and click "Sign In", the page refers to "https://secure.mydomain.com/catalog/index.php" where it's -supposed- to refer to: "https://secure.mydomain.com/store/catalog.index.php", right?.
Is this how one would setup a separate secure section on osC?.
I still can't get this going. For some reason, the "Sign In" still isn't working for me. It's as if it's feeding me back to a NONSSL filename on the HTTPS: domain. Ideas??..