Header Field Classification
|Reported by:||mnot@…||Owned by:|
|Component:||non-specific||Severity:||Active WG Document|
RFC2616 classifies headers (e.g., general, entity, request, response), but these classifications are sometimes misleading and often misused.
E.g., request-headers are defined as
The request-header fields allow the client to pass additional information about the request, and about the client itself, to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language method invocation.
We should discuss whether or not these classifications are helpful, and alternative approaches (e.g., allowing more than one classification for each header, to allow them to be more specific).
See also #104.
Change History (6)
comment:3 Changed 6 years ago by fielding@…
- Milestone changed from unassigned to 13
- Resolution set to incorporated
- Status changed from new to closed
comment:4 Changed 6 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:5 Changed 6 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed