<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://blog.teledyn.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>TeledyN - Sourcing the RSS Drain - Comments</title>
 <link>http://blog.teledyn.com/node/1499</link>
 <description>Comments for &quot;Sourcing the RSS Drain&quot;</description>
 <language>en</language>
<item>
 <title>Sourcing the RSS Drain</title>
 <link>http://blog.teledyn.com/node/1499</link>
 <description>&lt;p&gt;&lt;img src=&quot;http://www.heise.de/ix/artikel/2001/11/156/aufmacher.jpg&quot; alt=&quot;&quot; height=&quot;115&quot; width=&quot;150&quot; class=&quot;right&quot; /&gt; Seems I&#039;ve found the smoking gun &lt;a href=&quot;http://www.teledyn.com/mt/archives/001496.html&quot;&gt;draining my bandwidth over the &lt;span class=&quot;caps&quot;&gt;RSS &lt;/span&gt;feeds&lt;/a&gt;, and it&#039;s ironic that the airplay I get comes from &lt;a title=&quot;Seb&#039;s Open Research&quot; href=&quot;http://radio.weblogs.com/0110772/2003/11/25.html#a1257&quot;&gt;a Radio Userland Blog&lt;/a&gt; who likely learned about it from a blogroll tuned to my feed:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;There was a discussion around this topic about a year ago that seemed to lead to a satisfactory solution, but this muddies the waters. Is the problem confined to Drupal-served feeds? &lt;/i&gt;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;The culprit is definately &lt;u&gt;not&lt;/u&gt; Drupal.  That much is clear.  Drupal may be strict on the spec, but that&#039;s not even being tested in what is &lt;em&gt;really&lt;/em&gt; going awry: The culprit appears to be the &lt;em&gt;vast majority of &lt;span class=&quot;caps&quot;&gt;RSS &lt;/span&gt;reading clients who use the &lt;span class=&quot;caps&quot;&gt;HTTP &lt;/span&gt;&lt;code&gt;GET&lt;/code&gt; operator instead of using &lt;code&gt;HEAD&lt;/code&gt; first&lt;/em&gt; ... and the biggest offender appears to be Radio Userland! (may not be them, they are just the most numerous agent fetching this feed and their numbers approximately match the bytes served)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt;:&lt;/strong&gt; &lt;em&gt;drat&lt;/em&gt; ... just refined my test procedure and sure enough, 304 replies from my feed are devoid of the body, just as specified in the &lt;span class=&quot;caps&quot;&gt;RFC&lt;/span&gt; 2616, the world going according to plan.&lt;/p&gt;</description>
 <comments>http://blog.teledyn.com/node/1499#comments</comments>
 <category domain="http://blog.teledyn.com/taxonomy/term/6">the skin of culture</category>
 <pubDate>Tue, 25 Nov 2003 10:59:25 -0500</pubDate>
 <dc:creator>mrG</dc:creator>
 <guid isPermaLink="false">1499 at http://blog.teledyn.com</guid>
</item>
</channel>
</rss>
