#25 closed design (fixed)
Accept-Encoding BNF
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | Milestone: | 01 | |
Component: | p3-payload | Severity: | |
Keywords: | Cc: |
Description
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.
Change History (4)
comment:1 Changed 15 years ago by mnot@…
comment:2 Changed 15 years ago by julian.reschke@…
- Component set to payload
- Milestone set to 01
- Owner set to julian.reschke@…
- version set to d00
comment:3 Changed 15 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 15 years ago by julian.reschke@…
Fixed in [126]
The definition for Accept-Encoding should be revised: