W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

RE: HTTP 'HASH' Method

From: Eric Lawrence <ericlaw@exchange.microsoft.com>
Date: Thu, 24 May 2007 21:52:41 -0700
To: chown <elfius@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <8301DE7F96C0074C8DA98484623D7E51157CAB49E6@DF-MASTIFF-MSG.exchange.corp.microsoft.com>
See section 14.15 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html.

A properly behaving HTTP proxy and server will set explicit caching headers or ETAGs, which significantly reduces the need for a Content-MD5 header.  In practice, I've never seen it used.

Headers are not protected in HTTP; hence there's no real security value in this approach.
Eric Lawrence
Program Manager
Internet Explorer
Want to view and tamper with HTTP(S) traffic?
Try http://www.fiddler2.com<http://www.fiddler2.com/>

From: ietf-http-wg-request@w3.org [mailto:ietf-http-wg-request@w3.org] On Behalf Of chown
Sent: Thursday, May 24, 2007 9:37 PM
To: ietf-http-wg@w3.org
Subject: HTTP 'HASH' Method

I think a 'HASH' method should be implemented into HTTP, whereby the server responds with a hash (md5/sha) of the requested resource. This would be a godsend for large networks which tend to use caching extensively, because caching-proxy servers could verify the source hasn't changed while creating a minimal amount of traffic, thereby allow the amount of time the proxy stores cache to be be greatly increased only at the cost of hard drive space.
Not only would this benefit caching applications, but as I'm sure you could imagine, it could be used in may other fields, especially security.
Received on Friday, 25 May 2007 04:54:28 GMT

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