Plesk 10 and httpdocs and HttpsDocs - heads up

[adstock]

Hello,

after spending a week fighting to get a new server up with ASL 2.2 (that bit was easy) and Plesk 10 on a centOS 5 box i have discovered that there is no longer a httpsdocs folder and all your documents now sit under httpdocs.

This may not be a problem for most, but I have been coding my sites around this features as I started with Plesk 8 and it has always been there.

Tied to see if it was possible to hack the http.conf and vhost_ssl.conf file but it seems that the split directory will not be supported going forward.

Anybody running 9.5 and using these feature, I suggest you hang tight on the upgrade until some bright sparks has come up with a clean way of ensuring this is a not a problem (this is a hint to any forum members who might have an Idea how I can get around this problem and ensure that no one can http:// to files that I want accessed over Https.)

Cheers
adstock

[mikeshinn]

Huh, I didnt know they did that (we dont run 10 yet on our production boxes). So, if they did remove that capability one short term solution would be to use htaccess to force the connection over https. Heres an example:

RewriteRule ^path_to_ssl_content/(.*) https://www.example.com/path_to_ssl_content/$1 [R=301,L,NC]

Or you can do this:

RewriteCond %{HTTPS} !=on
RewriteRule ^path_to_ssl_content/(.*) https://%{SERVER_NAME}/path_to_ssl_content/$1 [R,L]

Which will auto rewrite the path, and will fill in the server name (so you could use this for multiple cnames, etc.)

Both will will re-write the URLs and will send the user to the https page (which could even be a different directory).

[breun]

So, it's no longer possible to serve different content for HTTP and HTTPS out of the box with Plesk 10?

[Snapdragon]

Just did a Google search on this and this thread was #1 .. so yeah, it looks like it's gone. I'm in the midst of a 10.1.1 deployment, moving from 9.5.

Long time no login .. took a bit of a break from IT, but I'm back. Bought EVERYTHING new for this rolllout - switches, servers, made the jump to iSCI SAN, new data center. So I'll probably be posting more here again

[breun]

Does anyone know what happens to sites that have different content in httpdocs and httpsdocs when upgrading Plesk to version 10?

[paulie]

Hi Breun,

I believe that during an upgrade it copes with it and keeps it, and warns you that its deprecated in Plesk 10. We have done a couple of test upgrades to Plesk 10 , but nothing extensive as we currently are a bit confused by the whole subscription thing!

Paul.

[BruceLee]

found this (scroll to last chapter). Maybe it's useful.
http://download1.parallels.com/Plesk/PP ... =65194.htm
I have read in another forum that after disabling compatibility mode it is not possible to activate it anymore.

[breun]

I'm not sure what I should be looking for at that link. I don't find anything relating to compatibility modes or httpdocs/httpsdocs.

[BruceLee]

sorry, here is the text I mentioned:
http://download1.parallels.com/Plesk/PP ... ser-guide/

Single httpdocs directory to contain all web content

The option to use a separate directory for storing web content that should be accessed over secure SSL connections is no longer available. All web content is now stored in a single directory - httpdocs.

The httpsdocs directory may remain in the webspace after upgrading to Parallels Plesk Panel 10, however, we recommend that you place all content in the httpdocs directory when uploading files to the webspace over FTP.

If you used the option to keep SSL-protected and all other content in separate directories, and had APS-packaged applications installed in the httpsdocs directory of a website, then after upgrade, the Panel will switch on the compatibility mode for that site. This will make the apps previously installed into httpsdocs directory accessible to the Internet users, but the apps will not be manageable through the Panel, and you will not be able to install new apps to the httpsdocs directory.

In such a case, if you have the necessary technical skills, you can do the following:

1. Back up all content from the httpsdocs directory and save it to another location. Do not move the files to httpdocs yet.
2. Back up databases used by applications installed in httpsdocs directory. You can do this with the help of the mysqldump utility.
3. Remove applications from the httpsdocs directory.
4. Switch off the compatibility mode through the Panel (at Websites & Domains tab > domain name).
5. Reinstall the required applications.
6. Upload the data you backed up on the step 1 to the httpdocs directory.
7. Restore the applications' databases by importing them to the MySQL database server.

If you are an inexperienced user, we recommend that you leave the previously installed applications and uploaded content in the httpsdocs directory, and host new applications on other websites. If you need to install apps on the site operating in compatibility mode, you can install them to the httpdocs (http://) location on that site.