<story><title>Fun With HTTP Headers</title><url>http://www.nextthing.org/archives/2005/08/07/fun-with-http-headers</url></story><parent_chain></parent_chain><comment><author>qw</author><text>The ultimate header is produced by a newspaper. Try running this line and see. It is a random line, so you might want to try it a few times :-)&lt;p&gt;&lt;pre&gt;&lt;code&gt;   curl -i -s --head http://www.vg.no/ | grep N&lt;/code&gt;&lt;/pre&gt;</text></comment>
<story><title>Fun With HTTP Headers</title><url>http://www.nextthing.org/archives/2005/08/07/fun-with-http-headers</url></story><parent_chain></parent_chain><comment><author>aristus</author><text>the &quot;Cneonction: close&quot; thing is a quirk of Netscaler loadbalancers. It&apos;s done to nullify any &quot;Connection: close&quot; headers the webserver spits out, as the Netscaler wants to manage it better. It&apos;s scrambled instead of removed so that it doesn&apos;t have to regenerate packets (length is the same) and it&apos;s scrambled semi-randomly so that people don&apos;t just assume it&apos;s a misspelling and add compatibility for it.</text></comment>