1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Problem with - Use a single directory for housing SSL and non-SSL content

Discussion in 'Plesk for Linux - 8.x and Older' started by mattbolton, May 18, 2005.

  1. mattbolton

    mattbolton Guest

    In Plesk 7.5.3 I noticed a handy new feature:
    Well, that should be great, keeps me from having to maintain two directories (httpdocs and httpsdocs) and keep them in sync.
    It works... sort of.
    Lets say I have a domain, "mydomain.com", and I have a subdomain "subd.mydomain.com". When using this new feature, all the content for "www.mydomain.com" whether accessed via HTTP or HTTPS now comes from the /httpdocs folder as expected.
    When it comes to the subdomain, the HTTP content comes from /subdomains/subd/httpdocs as expected... The unexpected part happens when trying to access the subdomain content via HTTPS.. it then uses the /httpdocs directory for the main domain rather than that of the subdomain. Does this make sense to anyone else? Or are my expectations unorthodox?
  2. faris

    faris Guest

    If that is what is happening then it sounds like a bug to me. Either that, or there is some sort of limitation that I'm not aware of relating to this feature.

    Unfortunately I've never used the Plesk subdomain facility, so I'm a little in the dark over how it works.

    Nevertheless, I'd contact Plesk support and get them to look into it. If it is a bug, is it a big but easy to fix one (I wold have thought) and they should really be told about it.