Ignore:
Timestamp:
Jan 3, 2008, 10:03:02 AM (12 years ago)
Author:
julian.reschke@…
Message:

Make the historical change information (RFC2068 -> RFC2616) complete again.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r137 r138  
    22752275<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    22762276<t>
     2277   Transfer-coding and message lengths all interact in ways that
     2278   required fixing exactly when chunked encoding is used (to allow for
     2279   transfer encoding that may not be self delimiting); it was important
     2280   to straighten out exactly how message lengths are computed.
     2281   (<xref target="entity.length"/>, see also <xref target="Part1"/>,
     2282   <xref target="Part5"/> and <xref target="Part6"/>).
     2283</t>
     2284<t>
    22772285   Charset wildcarding is introduced to avoid explosion of character set
    22782286   names in accept headers. (<xref target="header.accept-charset"/>)
Note: See TracChangeset for help on using the changeset viewer.