draft-mogul-http-digest

Last Version:	draft-mogul-http-digest-05.txt		Tracker Entry
Date:	02-Mar-2005
Disposition:	RFC3230 (diff)
Previous Versions:	draft-mogul-http-digest-05.txt (diff)    - 29-Mar-2004
	draft-mogul-http-digest-05.txt (diff)    - 18-Jan-2002
	draft-mogul-http-digest-04.txt (diff)    - 05-Oct-2001
	draft-mogul-http-digest-03.txt (diff)    - 07-Sep-2001
	draft-mogul-http-digest-02.txt (diff)    - 04-Oct-2000
	draft-mogul-http-digest-01.txt (diff)    - 09-Apr-2002
	draft-mogul-http-digest-00.txt (diff)    - 23-Feb-1999

A new Request for Comments is now available in online RFC libraries.


        RFC 3230

        Title:      Instance Digests in HTTP
        Author(s):  J. Mogul, A. Van Hoff
        Status:     Standards Track
        Date:       January 2002
        Mailbox:    JeffMogul@acm.org, avh@marimba.com
        Pages:      13
        Characters: 26846
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-mogul-http-digest-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3230.txt


HTTP/1.1 defines a Content-MD5 header that allows a server to include
a digest of the response body.  However, this is specifically defined
to cover the body of the actual message, not the contents of the full
file (which might be quite different, if the response is a
Content-Range, or uses a delta encoding).  Also, the Content-MD5 is
limited to one specific digest algorithm; other algorithms, such as
SHA-1 (Secure Hash Standard), may be more appropriate in some
circumstances.  Finally, HTTP/1.1 provides no explicit mechanism by
which a client may request a digest.  This document proposes HTTP
extensions that solve these problems.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.