[Q]: MD5 hash when serving byte ranges?!

[Martin Kraemer <Ma...@mch.sni.de>]

When browsing through http_core.c, I thought I saw that the MD5 hash is
built over the entire file, even when only byte ranges from the file are
served. From RFC2068, it is unclear to me whether this is correct. An
intermediate cache need not have the complete document in its cache, so
it cannot verify correct reception based on a hash that covers the whole
file.

Shouldn't the hash be built only over the byte range served?

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: [Q]: MD5 hash when serving byte ranges?!

[Dean Gaudet <dg...@arctic.org>]

But it doesn't need the complete document ... it can determine if it has
the same document by comparing md5s of the entire document.  That's the
only thing that's important ... isn't it?  Or is md5 intended to alleviate
the TCP/IP checksum failure probability?

Dean

On Sat, 25 Oct 1997, Martin Kraemer wrote:

> When browsing through http_core.c, I thought I saw that the MD5 hash is
> built over the entire file, even when only byte ranges from the file are
> served. From RFC2068, it is unclear to me whether this is correct. An
> intermediate cache need not have the complete document in its cache, so
> it cannot verify correct reception based on a hash that covers the whole
> file.
> 
> Shouldn't the hash be built only over the byte range served?
> 
>     Martin
> -- 
> | S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
> | ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
> | N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
> ~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
>