<?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: Modern-Day Frame Busting With X-FRAME-OPTIONS And &quot;This content cannot be displayed in a frame&quot; Warnings</title> <atom:link href="http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/feed/" rel="self" type="application/rss+xml" /><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/</link> <description>where things have nothing to do with beer - tutorials, tips, how-tos, thoughts, hacks, and other techy nonsense</description> <lastBuildDate>Sat, 11 Feb 2012 17:00:25 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Martin</title><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-52244</link> <dc:creator>Martin</dc:creator> <pubDate>Sun, 27 Nov 2011 02:38:44 +0000</pubDate> <guid
isPermaLink="false">http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-52244</guid> <description>There are many legitimate uses for using frames to connect sites of different origins.  I feel this development damages an important tool.  Any genuine security risks could be dealt with much more gracefully, rather than simply breaking a feature.
If kids are typing bad words into a computer you don&#039;t fix the problem by taking away the keyboard.</description> <content:encoded><![CDATA[<p>There are many legitimate uses for using frames to connect sites of different origins.  I feel this development damages an important tool.  Any genuine security risks could be dealt with much more gracefully, rather than simply breaking a feature.</p><p>If kids are typing bad words into a computer you don&#039;t fix the problem by taking away the keyboard.</p> ]]></content:encoded> </item> <item><title>By: Diana</title><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-52227</link> <dc:creator>Diana</dc:creator> <pubDate>Wed, 16 Nov 2011 04:58:20 +0000</pubDate> <guid
isPermaLink="false">http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-52227</guid> <description>Yes, but how do we rid our PC of this message when it pops up?
This content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.</description> <content:encoded><![CDATA[<p>Yes, but how do we rid our PC of this message when it pops up?</p><p>This content cannot be displayed in a frame</p><p> To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.</p> ]]></content:encoded> </item> <item><title>By: Roland</title><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-43546</link> <dc:creator>Roland</dc:creator> <pubDate>Thu, 15 Jul 2010 15:30:32 +0000</pubDate> <guid
isPermaLink="false">http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-43546</guid> <description>Seems to me like an option that will probably be used more for things it wasn&#039;t intended for than the things it was intended for.
I use noScript to block pages from doing all kinds of things I do not want, but here is accomplishes the opposite: it prevents me from looking a a page the way I want to.
The usability of sites like google image search will be limited more and more if sites start adding this header. I fear the moment wordpress, joomla, drupal, etc. make this header a default. It will basically make frames useless.
And unfortunately this &#039;protection&#039; only protects the sites that want to be protected, so it is very limited until it becomes the default way of working.
It should have been a browser setting, not a page header.
Pages that do not let themselves be molded to the wishes of the user, are annoying. That&#039;s why we all hate pop-ups, right-click protection, etc. And framebusting.
I know many web publishers find that their webpage should be viewed full screen, but that is not allways what I, the reader, the person they make their site for, want.
I fear that X-FRAME_OPTIONS will become the next weapon for publishers to enforce their wishes upon their readers, so I&#039;ve come to the conclusion that it is an annoyance, rather than a good thing.</description> <content:encoded><![CDATA[<p>Seems to me like an option that will probably be used more for things it wasn&#039;t intended for than the things it was intended for.</p><p>I use noScript to block pages from doing all kinds of things I do not want, but here is accomplishes the opposite: it prevents me from looking a a page the way I want to.<br
/> The usability of sites like google image search will be limited more and more if sites start adding this header. I fear the moment wordpress, joomla, drupal, etc. make this header a default. It will basically make frames useless.</p><p>And unfortunately this &#039;protection&#039; only protects the sites that want to be protected, so it is very limited until it becomes the default way of working.</p><p>It should have been a browser setting, not a page header.</p><p>Pages that do not let themselves be molded to the wishes of the user, are annoying. That&#039;s why we all hate pop-ups, right-click protection, etc. And framebusting.</p><p>I know many web publishers find that their webpage should be viewed full screen, but that is not allways what I, the reader, the person they make their site for, want.</p><p>I fear that X-FRAME_OPTIONS will become the next weapon for publishers to enforce their wishes upon their readers, so I&#039;ve come to the conclusion that it is an annoyance, rather than a good thing.</p> ]]></content:encoded> </item> <item><title>By: Artem Russakovskii</title><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-31910</link> <dc:creator>Artem Russakovskii</dc:creator> <pubDate>Fri, 29 Jan 2010 19:14:02 +0000</pubDate> <guid
isPermaLink="false">http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-31910</guid> <description>Thank you. Indeed, you&#039;re right. Corrected.</description> <content:encoded><![CDATA[<p>Thank you. Indeed, you&#039;re right. Corrected.</p> ]]></content:encoded> </item> <item><title>By: Ergomane</title><link>http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-31909</link> <dc:creator>Ergomane</dc:creator> <pubDate>Fri, 29 Jan 2010 18:41:52 +0000</pubDate> <guid
isPermaLink="false">http://beerpla.net/2009/10/29/modern-day-frame-busting-with-x-frame-options-and-this-content-cannot-be-displayed-in-a-frame-warnings/#comment-31909</guid> <description>AFAIK token is SAMEORIGIN, no dash.</description> <content:encoded><![CDATA[<p>AFAIK token is SAMEORIGIN, no dash.</p> ]]></content:encoded> </item> </channel> </rss>
