W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2006

RE: Large content size value

From: Travis Snoozy (Volt) <a-travis@microsoft.com>
Date: Fri, 29 Dec 2006 17:13:33 -0800
To: Jamie Lokier <jamie@shareable.org>
CC: David Morris <dwm@xpasc.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <86EDC3963F04D546BED8996F77D290F6049D117D31@NA-EXMSG-C138.redmond.corp.microsoft.com>

Jamie Lokier said:
> Travis Snoozy (Volt) wrote:
> > For reference, the size of the file is 4,368,281,840 bytes, 4GiB is
> > 4,294,967,295 bytes, and the difference is 73,314,545 bytes (the value
> > of Content-Length + 1). The actual GET returns a 501/Not Supported,
> > but the erroneous HEAD reply is still Bad and Wrong.
>
> Just a small note: 4GiB is 4,294,967,29_6_, and the difference is
> equal to the reported Content-Length.  Overflow is as expected for a
> 32-bit integer.

That's what I get for using "calculator" without thinking. Glad to see
you're paying attention, though ;).

> I wonder if it ever reports negative values like Content-Length: -1?

Nope; it appears to be an honest-to-goodness unsigned value (as it darn well
should be).

HEAD http://localhost/testdir/test2.gbg HTTP/1.1
Content-Length: 0
Host: localhost
Connection: close

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
X-Powered-By: ASP.NET
Connection: close
Date: Sat, 30 Dec 2006 00:52:28 GMT
Content-Type: application/octet-stream
Accept-Ranges: bytes
Last-Modified: Sat, 30 Dec 2006 00:50:54 GMT
ETag: "9183988fac2bc71:909"
Content-Length: 2346074112



-- Travis
Received on Saturday, 30 December 2006 01:13:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:53 GMT