Http->Https

[Illasera]

Hey all, I am hosting a website with an SSL protocol,My website has its own static IP address but it`s not linked via DNS to a domain name yet.At the moment, I am accessing my website via my static IP address,My files are hosted within a foldier named : httpdocs (PLASK interface system).Now i wish to build my Checkout page : (the payment page within my virtual store), So i link my store(Non-secured-httpdocs) to my checkout(secured-httpSdocs)(PLASK interface system).But since all of my pages are in a non-secured protocol and my checkout is, I am not sure how to redirect it, Since when i click the link, its still search for it within the unsecured directory(httpdocs).How do i make the transition between a non-secured page to a secured page.Also, is there anything i should know about how to set-up a secured page or its the same thing as a non-secured page, only the data transfer is encrypted?Thanks in advance.

[justsomeguy]

I'm not sure what PLASK is (do you mean Plesk?), but the servers I've worked with don't have separate web directories for secured vs non-secured content, everything is in the same place. You can mark a directory as requiring a secure connection, but it's still in the same web root as everything else. If you use https:// as the scheme in the link, then it should work assuming the server has SSL set up correctly. It may be that SSL connections are not enabled for your site. Do you have a certificate set up for the IP?

[Illasera]

Do you have a certificate set up for the IP?

Yes,and sorry, Plesk* is the right word, Meaningless name but ok.Now my Root directory have few SubDirectories (SAME ROOT, Few directories within the root), I can only use : Httpdocs directory andhttpSdocs directory (Assuming the S in the name stands for secured).Now, If all the files are going into a single directory, then why not having the entire websites have SSL encryption instead if just the selected pages?There must be someway to separate secured/non secured pages, I am assuming, 2 directories like i have, But i am not sure.Need a bit more clarification mate :)Thanks in advance.

[justsomeguy]

When I install a SSL certificate in IIS I just install the certificate for the IP. The web root is still c:\inetpub\wwwroot, or whatever it started as. For each individual web site or directory or file, I can specify that one directory or file requires an SSL connection. So, I can use a checkbox to say whether index.html needs to be accessed over HTTPS, or if it can also go through HTTP. There aren't two different files. If HTTPS is not required, I can type in the HTTP URL to load the file, and it loads. I can use https instead, and it still loads the same file. It's not looking for another file when the request goes over HTTPS.Now, that being said, it's possible to set up a server to serve SSL content from a different directory. Apache's configuration files let you set up a virtual host for any IP/hostname/port combo, so you can easily set it up so that port 80 has a certain directory as its web root, and port 443 has another. But doing so would mean that you can't just replace the URL with HTTPS, because the file might not exist in the other location. So, I'm not really sure why you would serve content from two different places for the same domain over HTTP or HTTPS, but I guess it's possible.http://www.google.com/search?client=opera&...-8&oe=utf-8

[Illasera]

When I install a SSL certificate in IIS I just install the certificate for the IP. The web root is still c:\inetpub\wwwroot, or whatever it started as. For each individual web site or directory or file, I can specify that one directory or file requires an SSL connection. So, I can use a checkbox to say whether index.html needs to be accessed over HTTPS, or if it can also go through HTTP. There aren't two different files. If HTTPS is not required, I can type in the HTTP URL to load the file, and it loads. I can use https instead, and it still loads the same file. It's not looking for another file when the request goes over HTTPS.Now, that being said, it's possible to set up a server to serve SSL content from a different directory. Apache's configuration files let you set up a virtual host for any IP/hostname/port combo, so you can easily set it up so that port 80 has a certain directory as its web root, and port 443 has another. But doing so would mean that you can't just replace the URL with HTTPS, because the file might not exist in the other location. So, I'm not really sure why you would serve content from two different places for the same domain over HTTP or HTTPS, but I guess it's possible.http://www.google.com/search?client=opera&...-8&oe=utf-8

I understand the fact that https is just a protocol and it doesnt require different page content, The only thing that is different is the encryption and the handshaking mathod.Why would i serve content from two difference places for the same domain? That`s what the host allows me, I have no access to any of the server config files or settings.. nor a special checkbox for secured/un-secured files...I dont recall if i wrote it before but , I didnt set up my SSL, my webhosting company did it for me... (Yea, sometimes i wish i could have used a virtual server, but i don`t).Thanks mate

[justsomeguy]

Why would i serve content from two difference places for the same domain?

I don't know why someone would decide to set the server up that way. I understand it's possible, but I don't know what benefit someone would think they get from it.