W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: CRLF requirement

From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Date: Sat, 5 Jul 2014 14:21:13 +0000
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <9A043F3CF02CD34C8E74AC1594475C738DED40D7@uxcn10-tdc06.UoA.auckland.ac.nz>
David Krauss <potswa@gmail.com> writes:

>Also, somehow the word Connection got munged to nnCoection. Never
>underestimate the expressive power of old-school C =97 I=92d wager that this
>is somehow the result of a typo where the backslash was omitted from =93\n=94
>in the source.

	/* The bizarre spellings are for NetApp NetCache servers, which 
	   unfortunately are widespread enough that we need to provide 
	   special-case handling for them.
	   
	   The reason why NetApp devices do this is because they think that 
	   they can manage connections better than the application that's 
	   creating them, so they rewrite "Connection: close" into something
	   that won't be recognised in order to avoid the connection 
	   actually being closed.  The reason for the 16-bit swap is because
	   the Fletcher checksum used in TCP/IP doesn't detect 16-bit word
	   swaps, so this allows the connection-control to be invalidated
	   without requiring a recalculation of the TCP checksum.  
		   
	   Someone probably got bonus pay for coming up with this */

Peter.
Received on Saturday, 5 July 2014 14:21:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC