18
votes

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
3

3 Answers

18
votes

The comments in https://basildoncoder.com/blog/turbocharging-net-webservice-clients.html say 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

3
votes

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

0
votes

I'm seeing a munged ntCoent-Length header without the correct version being present. The lack of a valid Content-Length is causing Mule ESB to throw an error out of the HTTP connector. Very annoying. I'm hoping our network team can control this with some Netscaler configuration.