views:

152

answers:

2

I get the following HTTP response headers in a particular response. All looks okay. However I have noticed that the content-length appears twice...

Content-Length: 2424 ntCoent-Length: 2424

Is there a particular reason why the content-length is returned a second time as ntCoent-Length?

HTTP/1.0 200 OK
Date: Wed, 26 May 2010 09:38:19 GMT
Server: Apache
P3P: CP="NOI DSP COR CURa ADMa TA1a OUR BUS IND UNI COM NAV INT"
Accept-Charset: iso-8859-1, unicode-1-1;q=0.8
Expires: Sun, 15 Jul 1990 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache
Content-Language: en
ntCoent-Length: 2424
Connection: close
Content-Type: text/html;charset=iso-8859-1
Content-Length: 2424
+4  A: 

http://basildoncoder.com/blog/2007/12/15/turbocharging-net-webservice-clients/ says the jumbled ntCoent-Length header contains the uncompressed size of the response.

You should see the Content-Length is smaller than ntCoent-Length in cases where Content-Encoding:gzip or similar

JoseK
Thats is what I thought it was used for. Good to get it clarified. Is this common practice?
DMcKenna
I cant find this documented in any RFC, though it shows in all response headers.
JoseK
A: 

FYI, HTTP headers from some clients have characters randomly replaced gives other examples of letter transposition in http headers.

Kevin Hakanson