 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Trenches &#187; Chrome</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-trenches/tag/chrome/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/it-trenches</link>
	<description></description>
	<lastBuildDate>Fri, 19 Nov 2010 14:37:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Google has published a browser security handbook for developers</title>
		<link>http://itknowledgeexchange.techtarget.com/it-trenches/google-has-published-a-browser-security-handbook-for-developers/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-trenches/google-has-published-a-browser-security-handbook-for-developers/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 13:02:55 +0000</pubDate>
		<dc:creator>Troy Tate</dc:creator>
				<category><![CDATA[browser]]></category>
		<category><![CDATA[browser security]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[Safari]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[web security]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-trenches/google-has-published-a-browser-security-handbook-for-developers/</guid>
		<description><![CDATA[If you develop websites or manage webservices, then you should check out the Browser Security Handbook that Google publishes on their code.google.com website. The Browser Security Handbook currently has three sections: Part 1: Basic concepts behind web browsers Uniform Resource Locators Unicode in URLs True URL schemes Pseudo URL schemes Hypertext Transfer Protocol Hypertext Markup [...]]]></description>
				<content:encoded><![CDATA[<p>If you develop websites or manage webservices, then you should check out the <a href="http://code.google.com/p/browsersec/wiki/Main" target="_blank">Browser Security Handbook</a> that Google publishes on their <a href="http://code.google.com" target="_blank">code.google.com</a> website. The Browser Security Handbook currently has three sections:</p>
<p>Part 1: Basic concepts behind web browsers</p>
<ul>
<li>Uniform Resource Locators
<ul>
<li>Unicode in URLs</li>
</ul>
</li>
<li>True URL schemes</li>
<li>Pseudo URL schemes</li>
<li>Hypertext Transfer Protocol</li>
<li>Hypertext Markup Language
<ul>
<li>HTML entity encoding</li>
</ul>
</li>
<li>Document Object Model</li>
<li>Browser-side Javascript
<ul>
<li>Javascript character encoding</li>
</ul>
</li>
<li>Other document scripting languages</li>
<li>Cascading stylesheets
<ul>
<li>CSS character encoding</li>
</ul>
</li>
<li>Other built-in document formats</li>
<li>Plugin-supported content</li>
</ul>
<p>Part 2: Standard browser security features</p>
<ul>
<li>Same-origin policy
<ul>
<li>Same-origin policy for DOM access</li>
<li>Same-origin policy for XMLHttpRequest</li>
<li>Same-origin policy for cookies</li>
<li>Same-origin policy for Flash</li>
<li>Same-origin policy for Java</li>
<li>Same-origin policy for Silverlight</li>
<li>Same-origin policy for Gears</li>
<li>Origin inheritance rules</li>
<li>Cross-site scripting and same-origin policies</li>
</ul>
</li>
<li>Life outside same-origin rules
<ul>
<li>Navigation and content inclusion across domains</li>
<li>Arbitrary page mashups (UI redressing)</li>
<li>Gaps in DOM access control</li>
<li>Privacy-related side channels</li>
</ul>
</li>
<li>Various network-related restrictions
<ul>
<li>Local network / remote network divide</li>
<li>Port access restrictions</li>
<li>URL scheme access rules</li>
<li>Redirection restrictions</li>
<li>International Domain Name checks</li>
<li>Simultaneous connection limits</li>
</ul>
</li>
<li>Third-party cookie rules</li>
<li>Content handling mechanisms
<ul>
<li>Survey of content sniffing behaviors</li>
<li>Downloads and Content-Disposition</li>
<li>Character set handling and detection</li>
<li>Document caching</li>
</ul>
</li>
<li>Defenses against disruptive scripts
<ul>
<li>Popup and dialog filtering logic</li>
<li>Window appearance restrictions</li>
<li>Execution timeouts and memory limits</li>
<li>Page transition logic</li>
</ul>
</li>
<li>Protocol-level encryption facilities</li>
</ul>
<p>Part 3: Experimental and legacy security mechanisms</p>
<ul>
<li>HTTP authentication</li>
<li>Name look-ahead and content prefetching</li>
<li>Password managers</li>
<li>Microsoft Internet Explorer zone model</li>
<li>Microsoft Internet Explorer frame restrictions</li>
<li>Mozilla and Safari HTML5 storage experiments</li>
<li>Microsoft Internet Explorer XSS filtering</li>
<li>Script restriction frameworks</li>
<li>Origin headers</li>
<li>Mozilla content security policies</li>
</ul>
<p>This is a good resource for developers and administrators to understand browser &amp; web security considerations.</p>
<p>Thanks for reading and let&#8217;s continue to be good network citizens.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-trenches/google-has-published-a-browser-security-handbook-for-developers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
