<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Redirect to https (SSL) in php</title>
	<atom:link href="http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 01:35:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Arnab Bhattacharjee</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-13280</link>
		<dc:creator>Arnab Bhattacharjee</dc:creator>
		<pubDate>Thu, 19 Jan 2012 10:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-13280</guid>
		<description>Nice code. It is changing the entire site to https. But how could I exclude cgi-bin folder from this effect. There are some cgi scripts kept in this folder, and they are calling by cronjob. 

If the entire site follows the https protocol the scripts are not working properly.</description>
		<content:encoded><![CDATA[<p>Nice code. It is changing the entire site to https. But how could I exclude cgi-bin folder from this effect. There are some cgi scripts kept in this folder, and they are calling by cronjob. </p>
<p>If the entire site follows the https protocol the scripts are not working properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niranjan</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-13230</link>
		<dc:creator>Niranjan</dc:creator>
		<pubDate>Fri, 05 Aug 2011 09:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-13230</guid>
		<description> Many many thanks it helped me </description>
		<content:encoded><![CDATA[<p> Many many thanks it helped me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mailtoitkarthi</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-10261</link>
		<dc:creator>Mailtoitkarthi</dc:creator>
		<pubDate>Sat, 18 Sep 2010 09:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-10261</guid>
		<description>Very Very Thanks.... it is very useful..</description>
		<content:encoded><![CDATA[<p>Very Very Thanks&#8230;. it is very useful..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-8830</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Thu, 06 May 2010 18:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-8830</guid>
		<description>Thank you! I have been trying to find a simple way to do this.</description>
		<content:encoded><![CDATA[<p>Thank you! I have been trying to find a simple way to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-10224</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Thu, 06 May 2010 18:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-10224</guid>
		<description>Thank you! I have been trying to find a simple way to do this.</description>
		<content:encoded><![CDATA[<p>Thank you! I have been trying to find a simple way to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Paarlberg</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-1503</link>
		<dc:creator>Simon Paarlberg</dc:creator>
		<pubDate>Sat, 11 Apr 2009 21:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-1503</guid>
		<description>Hi good explanation. I have some real world experience to add;

When using PHP to redirect to the secure connection, it&#039;s a bad idea to redirect the payload (ex. ?password=something_secret) directly to the script. The reason for this is, that you or your users will usually not know that the information has been passed through an unsecure connection.
In this case you should make sure that everybody knows that an embarrassing error has been made, so it motivates you to correct the flaw. Otherwise such a mistake, can exist for years without you knowing it and thus render the SSL tunnel less secure. Remember all it takes is the session-id and someone evil can gain access to you session.

I always send the user back to the login prompt while giving them a new session-id. Then all should be OK :-)</description>
		<content:encoded><![CDATA[<p>Hi good explanation. I have some real world experience to add;</p>
<p>When using PHP to redirect to the secure connection, it&#8217;s a bad idea to redirect the payload (ex. ?password=something_secret) directly to the script. The reason for this is, that you or your users will usually not know that the information has been passed through an unsecure connection.<br />
In this case you should make sure that everybody knows that an embarrassing error has been made, so it motivates you to correct the flaw. Otherwise such a mistake, can exist for years without you knowing it and thus render the SSL tunnel less secure. Remember all it takes is the session-id and someone evil can gain access to you session.</p>
<p>I always send the user back to the login prompt while giving them a new session-id. Then all should be OK <img src='http://www.phpgenious.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Paarlberg</title>
		<link>http://www.phpgenious.com/2009/03/redirect-to-https-ssl-in-php/comment-page-1/#comment-10223</link>
		<dc:creator>Simon Paarlberg</dc:creator>
		<pubDate>Sat, 11 Apr 2009 21:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpgenious.com/?p=284#comment-10223</guid>
		<description>Hi good explanation. I have some real world experience to add;

When using PHP to redirect to the secure connection, it&#039;s a bad idea to redirect the payload (ex. ?password=something_secret) directly to the script. The reason for this is, that you or your users will usually not know that the information has been passed through an unsecure connection.
In this case you should make sure that everybody knows that an embarrassing error has been made, so it motivates you to correct the flaw. Otherwise such a mistake, can exist for years without you knowing it and thus render the SSL tunnel less secure. Remember all it takes is the session-id and someone evil can gain access to you session.

I always send the user back to the login prompt while giving them a new session-id. Then all should be OK :-)</description>
		<content:encoded><![CDATA[<p>Hi good explanation. I have some real world experience to add;</p>
<p>When using PHP to redirect to the secure connection, it&#8217;s a bad idea to redirect the payload (ex. ?password=something_secret) directly to the script. The reason for this is, that you or your users will usually not know that the information has been passed through an unsecure connection.<br />
In this case you should make sure that everybody knows that an embarrassing error has been made, so it motivates you to correct the flaw. Otherwise such a mistake, can exist for years without you knowing it and thus render the SSL tunnel less secure. Remember all it takes is the session-id and someone evil can gain access to you session.</p>
<p>I always send the user back to the login prompt while giving them a new session-id. Then all should be OK <img src='http://www.phpgenious.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
