Ticket #224 (closed design: fixed)
Header Field Classification
|Reported by:||email@example.com||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.
- Status changed from new to closed
- Resolution set to incorporated
- Milestone changed from unassigned to 13
- Status changed from closed to reopened
- Resolution incorporated deleted
- Status changed from reopened to closed
- Resolution set to fixed