Published RFCs never change. Although every published RFC has been submitted to careful proofreading by the RFC Editor and the author (s), errors do sometimes go undetected. As a service to the readers of RFCs, this page contains a list of technical and editorial errors that have been reported to the RFC Editor and verified by the authors or the IESG.

In general, we cannot guarantee the correctness of these errata; the reader must make his/her own judgment.
Erratum for RFC 2616

RFC 2616, "Hypertext Transfer Protocol -- HTTP/1.1", June 1999

All known errata for this HTTP RFC will be found at:
http://purl.org/NET/http-errata and
http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/

Reported By: "WooJin Chung" <creativechoice@gmail.com>
Date: Wed, 1 Nov 2006 15:13:50 +0900

UNVERIFIED
Section 4.4 says:

 4.  If the message uses the media type "multipart/byteranges", and the
      ransfer-length is not otherwise specified, then this self-
      elimiting media type defines the transfer-length.
It should say:
 4.  If the message uses the media type "multipart/byteranges", and the
      transfer-length is not otherwise specified, then this self-
      elimiting media type defines the transfer-length.