Opened 7 years ago

Closed 6 years ago

Last modified 5 years ago

#224 closed design (fixed)

Header Field Classification

Reported by: mnot@… Owned by:
Priority: normal Milestone: 13
Component: non-specific Severity: Active WG Document
Keywords: Cc:

Description

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:1 Changed 7 years ago by mnot@…

Agreement in Maastricht that header classification is less than useful.

comment:2 Changed 6 years ago by fielding@…

From [1163]:

Remove header field classifications.

Addresses #224 and #104

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

comment:6 Changed 5 years ago by julian.reschke@…

  • Summary changed from Header Classification to Header Field Classification
Note: See TracTickets for help on using tickets.