Changeset 85 for draft-ietf-httpbis

Timestamp:

21/12/07 23:35:30 (14 years ago)

Author:

fielding@…

Message:

Resolve #16: Remove 'identity' token references

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.xml (modified) (3 diffs)
• p3-payload.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1175 +1175 @@
    The Internet Assigned Numbers Authority (IANA) acts as a registry for
    transfer-coding value tokens. Initially, the registry contains the
-   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>), "identity" (section
-   3.6.2), "gzip" (&payload;), "compress" (&payload;), and "deflate"
-   (&payload;).
+   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>),
+   "gzip" (&payload;), "compress" (&payload;), and "deflate" (&payload;).
 </t>
 <t>
@@ -1437 +1436 @@
     </t></x:lt>
     <x:lt><t>
-     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>) is present and
-     has any value other than "identity", then the transfer-length is
+     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
+     is present, then the transfer-length is
      defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>),
      unless the message is terminated by closing the connection.
@@ -1490 +1489 @@
 <t>
    Messages &MUST-NOT; include both a Content-Length header field and a
-   non-identity transfer-coding. If the message does include a non-identity
+   transfer-coding. If the message does include a
    transfer-coding, the Content-Length &MUST; be ignored.
 </t>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -2306 +2306 @@
 <section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
 <t>
-   HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC
+   HTTP does not use the Content-Transfer-Encoding field of RFC
    2045. Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
-   remove any non-identity CTE ("quoted-printable" or "base64") encoding
+   remove any Content-Transfer-Encoding
    prior to delivering the response message to an HTTP client.
 </t>