Opened 10 years ago
Closed 10 years ago
#424 closed editorial (incorporated)
Absence of Accept-Encoding
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 22 |
Component: | p2-semantics | Severity: | In WG Last Call |
Keywords: | Cc: |
Description
A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response.
This statement confused a browser vendor I was talking to, because "accept" is misleading here; it implies that the client is capable of processing any encoding. It would be more accurate to say:
A request without an Accept-Encoding header field does not indicate the content-codings (if any) that the user agent finds acceptable.
or
A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response. Note that the user agent might not be able to process an encoding sent in response to such a request.
If we intend servers to be able to infer something from *that*, we should say so directly.
Change History (3)
comment:1 Changed 10 years ago by mnot@…
- Owner draft-ietf-httpbis-p2-semantics@… deleted
comment:2 Changed 10 years ago by fielding@…
comment:3 Changed 10 years ago by fielding@…
- Milestone changed from unassigned to 22
- Resolution set to incorporated
- Status changed from new to closed
From [2084]:
(editorial) Clarify that no Accept-Encoding means that the user agent has no prefereence, not that it must implement all possible codings; addresses #424