Re: checking for and enforcing https

From: Date: Tue, 26 Feb 2008 18:11:54 +0000
Subject: Re: checking for and enforcing https
References: 1 2 3 4 5 6 7 8 9  Groups: php.general 
Request: Send a blank email to php-general+get-270207@lists.php.net to get a copy of this message
At 12:10 PM -0500 2/26/08, Daniel Brown wrote:
On Tue, Feb 26, 2008 at 11:54 AM, tedd <tedd.sperling@gmail.com> wrote:
At present, I use the actual directories (http/https) to determine if the operation of the script is secure or not.
    You also hijack other people's threads.  No-no, Tedd!  *slaps hand*
It's a related hijack. And, it's "hijacked" (grammar police). At 9:51 AM -0800 2/26/08, Warren Vail wrote:
Most of my ISP's setup their servers to pull from the same base path for both secure forms and non-secure forms, and I use something similar to below to enforce the right one is being used. One of the benefits of doing this is I can imbed the same images and graphics by using the same business path for them and only changing the protocol (https). Most browsers will complain if you imbed http images in a https form.
You guys rock! You gave me a different perspective of what http and https is. I was thinking it was an inherited directory thing when it's actually a protocol that can be declared regardless of where the scripts are located. Mondo cool -- and that also solves the image problem I ran into some time ago. Thanks everyone. tedd -- ------- http://sperling.com http://ancientstones.com http://earthstones.com

« previous php.general (#270207) next »