Changeset 85


Ignore:
Timestamp:
Dec 21, 2007, 3:35:30 PM (12 years ago)
Author:
fielding@…
Message:

Resolve #16: Remove 'identity' token references

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r84 r85  
    11751175   The Internet Assigned Numbers Authority (IANA) acts as a registry for
    11761176   transfer-coding value tokens. Initially, the registry contains the
    1177    following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>), "identity" (section
    1178    3.6.2), "gzip" (&payload;), "compress" (&payload;), and "deflate"
    1179    (&payload;).
     1177   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>),
     1178   "gzip" (&payload;), "compress" (&payload;), and "deflate" (&payload;).
    11801179</t>
    11811180<t>
     
    14371436    </t></x:lt>
    14381437    <x:lt><t>
    1439      If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>) is present and
    1440      has any value other than "identity", then the transfer-length is
     1438     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
     1439     is present, then the transfer-length is
    14411440     defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>),
    14421441     unless the message is terminated by closing the connection.
     
    14901489<t>
    14911490   Messages &MUST-NOT; include both a Content-Length header field and a
    1492    non-identity transfer-coding. If the message does include a non-identity
     1491   transfer-coding. If the message does include a
    14931492   transfer-coding, the Content-Length &MUST; be ignored.
    14941493</t>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r81 r85  
    23062306<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
    23072307<t>
    2308    HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC
     2308   HTTP does not use the Content-Transfer-Encoding field of RFC
    23092309   2045. Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
    2310    remove any non-identity CTE ("quoted-printable" or "base64") encoding
     2310   remove any Content-Transfer-Encoding
    23112311   prior to delivering the response message to an HTTP client.
    23122312</t>
Note: See TracChangeset for help on using the changeset viewer.