Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've done some basic HTTPS sites on my shared hosting, but in my hosting provider the folders in filesystem are different for SSL and the regular website. Is this an option, or is it required for the two to be separate? That is, loads a different folder on the virtual host as opposed to

If the file folders are different, then what should I do about session storage if it is a custom session storage that is stored in my websites filesystem that is different between HTTP and HTTPS sites? And what about other files, such as users custom-uploaded files, do I have to sync them somewhat?

If I set up my own server, then is it possible for me to run HTTPS and HTTP from the same folder?

Thank you!

share|improve this question

closed as off topic by Zoredache, John Gardeniers, Ward, Michael Hampton, Ladadadada Oct 5 '12 at 13:32

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

If I set up my own server, then is it possible for me to run HTTPS and HTTP - Yes. As for the rest, you will probably need to work with your provider. – Zoredache Oct 1 '12 at 19:00
up vote 2 down vote accepted

It is not required that SSL and non-SSL filesystems be different, they can point to the same directory. In my experience, if they are separate, it is generally due to trying to keep the server code clean and to ensure that any and all resources needed for SSL are available under the SSL folder (i.e. avoid the "some resources were not loaded because they were not secure" browser error).

A common option for sharing code/resources is to enable sym-links (Apache?) and then in the SSL version simply reference the symlinks that point to the original files so that they are effectively "shared" by both directories.

share|improve this answer
Thanks! That's what I needed to hear :) – kristovaher Oct 1 '12 at 19:12
No prob, glad it helped! – landonz Oct 1 '12 at 20:23

Not the answer you're looking for? Browse other questions tagged or ask your own question.