<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: perldotcom</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/perldotcom.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-01-20T09:49:06+00:00</updated><author><name>Simon Willison</name></author><entry><title>Dangers of remote Javascript</title><link href="https://simonwillison.net/2008/Jan/20/dangers/#atom-tag" rel="alternate"/><published>2008-01-20T09:49:06+00:00</published><updated>2008-01-20T09:49:06+00:00</updated><id>https://simonwillison.net/2008/Jan/20/dangers/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://radar.oreilly.com/archives/2008/01/dangers_of_remo.html"&gt;Dangers of remote Javascript&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Perl.com got hit by a JavaScript porn redirect when the domain of one of their advertisers expired and was bought by a porn company. Nat Torkington suggests keeping track of the expiration dates on any third party domains that are serving JavaScript on your site.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nat-torkington"&gt;nat-torkington&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/perldotcom"&gt;perldotcom&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xss"&gt;xss&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="javascript"/><category term="nat-torkington"/><category term="oreilly"/><category term="perldotcom"/><category term="security"/><category term="xss"/></entry></feed>