httpbis: Ticket #25: Accept-Encoding BNF

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/25

Origin:  http://www.w3.org/mid/429F0D20.3000306@yahoo.com

Component: p3-payload

In section 14.3, the definition of Accept-Encoding is given as follows:

Accept-Encoding  = "Accept-Encoding" ":"
1#( codings [ ";" "q" "=" qvalue ] )

This definition implies that there must be at least one non-null codings. However, just below this definition, one of the examples given has an empty Accept-Encoding field-value:

Accept-Encoding: compress, gzip
Accept-Encoding:
Accept-Encoding: *
Accept-Encoding: compress;q=0.5, gzip;q=1.0
Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0

Furthermore, the fourth rule for testing whether a content-coding is acceptable mentions the possibility that the field-value may be empty.

Mails

Mails by Sender (Top 10) Mails by Month

Associated Checkins

julian.reschke@gmx.de (Tue, 01 Jan 2008 14:58:59 GMT)
[126]: Resolve #25: Accept-Encoding can have zero elements.

History

: comment added (Thu, 20 Dec 2007 03:21:01 GMT)

The definition for Accept-Encoding should be revised:

Accept-Encoding  = "Accept-Encoding" ":"
                #( codings [ ";" "q" "=" qvalue ] )

: comment added; owner, version, component, milestone set (Tue, 01 Jan 2008 12:28:44 GMT)

Resolving as per < http://greenbytes.de/tech/webdav/draft-lafon-rfc2616bis-04.html#rfc.issue.i25-accept-encoding-bnf > and < http://www.w3.org/2007/03/18-rfc2616-minutes.html#action09 >.

: comment added; resolution set; status changed (Tue, 01 Jan 2008 12:34:54 GMT)

: comment added (Tue, 01 Jan 2008 14:58:59 GMT)

Fixed in [126]

Related Information

Issues List Index