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/p6-cache.xml

    r137 r138  
    28172817<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    28182818<t>
     2819   Transfer-coding and message lengths all interact in ways that
     2820   required fixing exactly when chunked encoding is used (to allow for
     2821   transfer encoding that may not be self delimiting); it was important
     2822   to straighten out exactly how message lengths are computed.
     2823   (<xref target="non-modifiable.headers"/>,
     2824   see also <xref target="Part1"/>, <xref target="Part3"/> and <xref target="Part5"/>)
     2825</t>
     2826<t>
    28192827   A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
    28202828   was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
Note: See TracChangeset for help on using the changeset viewer.