* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #16 (closed editorial: fixed)

Opened 7 years ago

Last modified 6 years ago

Remove 'identity' token references

Reported by: mnot@pobox.com Owned by:
Priority: Milestone: 01
Component: non-specific Severity:
Keywords: Cc:
Origin: http://lists.w3.org/Archives/Public/ietf-http-wg-old/2001SepDec/0018.html

Description

The "identity" transfer coding was removed, but some references to it were not.

In section 3.6, remove reference to non-existant section

The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry contains the following tokens: "chunked" (section 3.6.1), "identity" (section 3.6.2), "gzip" (section 3.5), "compress" (section 3.5), and "deflate" (section 3.5).

It should be:

The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry contains the following tokens: "chunked" (section 3.6.1), "gzip" (section 3.5), "compress" (section 3.5), and "deflate" (section 3.5).

In section 4.4 remove 'other than identity' for Transfer-Encoding case since identity is not a valid value.

2.If a Transfer-Encoding header field (section 14.41) is present and has any value other than "identity", then the transfer-length is defined by use of the "chunked" transfer-coding (section 3.6), unless the message is terminated by closing the connection.

It should be:

2.If a Transfer-Encoding header field (section 14.41) is present, then the transfer-length is defined by use of the "chunked" transfer-coding (section 3.6), unless the message is terminated by closing the connection.

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, the Content-Length MUST be ignored.

It should be:

Messages MUST NOT include both a Content-Length header field and a transfer-coding. If the message does include a transfer-coding, the Content-Length MUST be ignored.

In section 19.4.5 remove 'identity' CTE.

HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP MUST remove any non-identity CTE ("quoted-printable" or "base64") encoding prior to delivering the response message to an HTTP client.

It should be:

HTTP does not use the Content-Transfer-Encoding field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP MUST remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.

Change History

comment:1 Changed 7 years ago by fielding@gbiv.com

  • Status changed from new to closed
  • version set to 00
  • Resolution set to fixed
  • Milestone set to 01

Fixed in [85]

comment:2 Changed 7 years ago by mnot@pobox.com

  • version changed from 00 to d00

comment:3 Changed 6 years ago by julian.reschke@gmx.de

  • Component set to non-specific
Note: See TracTickets for help on using tickets.