<?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: Browser Referrer Insecurities</title>
	<atom:link href="http://michaeldaw.org/news/news-231106-0/feed" rel="self" type="application/rss+xml" />
	<link>http://michaeldaw.org/news/news-231106-0</link>
	<description>Weekly humour</description>
	<lastBuildDate>Thu, 07 May 2009 20:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/news/news-231106-0/comment-page-1#comment-1944</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Sat, 16 Dec 2006 09:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/news/news-231106-0/#comment-1944</guid>
		<description>Mark its an interesting point to only send the base URL as part of the referrer rather then the entire base URL + query string. 

My concern and reason for the original post is that of privacy. Why should anyone else on the Internet know where you have been? A number of firewalling products already filter out the referrer header. 

As to your point regarding security. The referrer field can be spoofed anyways, so it doesn&#039;t provide the level of security you would expect. Also, you may be limiting alot of your site visitors by using it in this way.</description>
		<content:encoded><![CDATA[<p>Mark its an interesting point to only send the base URL as part of the referrer rather then the entire base URL + query string. </p>
<p>My concern and reason for the original post is that of privacy. Why should anyone else on the Internet know where you have been? A number of firewalling products already filter out the referrer header. </p>
<p>As to your point regarding security. The referrer field can be spoofed anyways, so it doesn&#8217;t provide the level of security you would expect. Also, you may be limiting alot of your site visitors by using it in this way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark IJbema</title>
		<link>http://michaeldaw.org/news/news-231106-0/comment-page-1#comment-1909</link>
		<dc:creator>Mark IJbema</dc:creator>
		<pubDate>Sat, 16 Dec 2006 00:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/news/news-231106-0/#comment-1909</guid>
		<description>You&#039;re right you shouldn&#039;t use the referrer for security, but i still think it&#039;s worth to use it for defense in depth. If i have a webapp, i *never* want serve an internal page when the referrer is another site. Maybe it would be better to show only the site to external sites as referrere? So in your example instead of:

Referer: http://www.google.com.br/search?q=*Hidden for privacy*&amp;hl=pt-BR

send the following header:
Referer: http://www.google.com.br/

Or maybe even
Referer: http://not-your-site.example.org/

But why make it blank, i don&#039;t see the use of that...</description>
		<content:encoded><![CDATA[<p>You&#8217;re right you shouldn&#8217;t use the referrer for security, but i still think it&#8217;s worth to use it for defense in depth. If i have a webapp, i *never* want serve an internal page when the referrer is another site. Maybe it would be better to show only the site to external sites as referrere? So in your example instead of:</p>
<p>Referer: <a href="http://www.google.com.br/search?q=" rel="nofollow">http://www.google.com.br/search?q=</a>*Hidden for privacy*&amp;hl=pt-BR</p>
<p>send the following header:<br />
Referer: <a href="http://www.google.com.br/" rel="nofollow">http://www.google.com.br/</a></p>
<p>Or maybe even<br />
Referer: <a href="http://not-your-site.example.org/" rel="nofollow">http://not-your-site.example.org/</a></p>
<p>But why make it blank, i don&#8217;t see the use of that&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
