Re: checking for and enforcing https
| From: | Daniel Brown | Date: | Tue, 26 Feb 2008 21:46:38 +0000 |
| Subject: | Re: checking for and enforcing https | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-270236@lists.php.net to get a copy of this message | ||
On Tue, Feb 26, 2008 at 4:06 PM, Shawn McKenzie <nospam@mckenzies.net> wrote:
> When most people talk about a http and https directory, they are most
> likely talking about the common convention in shared hosting especially
> on Apache where your account will have a httpdocs/ and a httpsdocs/
> directory or similar. Apache sets the docroot depending upon what
> protocol is used http or https. It seems fairly common.
That's not Apache-centric though. It's based upon the layout of
the operating system or control panel architecture, and it's not
really all too common. I believe Plesk and Helm may use it, but by
default (and in cPanel), your web files will normally go to
~/public_html/ for everything, and then HTTPS/SSL connections simply
encrypt everything served from there when called, as opposed to
non-encrypted content-serving on standard HTTP.
Of course, getting into that is a completely different discussion
from the post made by the OP.... whom, as it appears, gave up and took
off when Tedd *hijacked* his thread. ;-P
--
</Dan>
Daniel P. Brown
Senior Unix Geek
<? while(1) { $me = $mind--; sleep(86400); } ?>