* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #231 (closed design: fixed)

Opened 4 years ago

Last modified 2 years ago

Considerations for new header fields

Reported by: mnot@pobox.com Owned by: mnot@pobox.com
Priority: normal Milestone: 17
Component: non-specific Severity: Active WG Document
Keywords: Cc:
Origin:

Description (last modified by mnot@pobox.com) (diff)

We need to document what those who want to define new headers need to take into consideration. E.g.,

  • i18n / charset
  • reuse of common syntax
  • whether it's required to be listed in the connection header (hop-by-hop vs. end-to-end)
    • request or response?
    • payload?
    • allowable in trailers?
    • how intermediaries should/should not handle them
    • special handling of Content-*, in case we keep this (pulled into this bug from [180])
    • target of metadata (see #20, etc.)
    • whether the header should be preserved across redirects

Not sure if this should go in p1 or p2.

Attachments

231.diff (6.4 KB) - added by julian.reschke@gmx.de 3 years ago.
proposed change for p2

Change History

comment:1 Changed 4 years ago by julian.reschke@gmx.de

  • Description modified (diff)

comment:2 Changed 4 years ago by mnot@pobox.com

  • Owner set to mnot@pobox.com

comment:3 Changed 4 years ago by julian.reschke@gmx.de

When using common syntax like "param", how to handle repetitions. (1) Are they allowed? (2) What are the processing requirements?

comment:4 Changed 4 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 12

comment:5 Changed 4 years ago by julian.reschke@gmx.de

  • Milestone changed from 12 to 13

comment:6 Changed 3 years ago by mnot@pobox.com

Note somewhere that 'close' is reserved ( see #256 ).

comment:7 Changed 3 years ago by fielding@gbiv.com

From [1158]:

Replaced the general prohibition on unrecognized Content-* header fields with a specific prohibition of Content-Range (the only field for which it is an actual problem) and a general requirement regarding checking for consistency. Unfortunately, this required rewriting the entire section on PUT to get rid of the misconceptions about storing resources and reflect how PUT is actually implemented in practice.

Addresses #79, #102, #103, #104, #112, #180, #231, and #267

comment:8 Changed 3 years ago by mnot@pobox.com

  • Milestone changed from 13 to 14

comment:9 Changed 3 years ago by mnot@pobox.com

  • Description modified (diff)

comment:10 Changed 3 years ago by julian.reschke@gmx.de

  • Milestone changed from 14 to 15

comment:11 Changed 3 years ago by mnot@pobox.com

  • Milestone changed from 15 to unassigned

Unassigning milestone; please don't set a milestone on a design ticket until we have WG consensus, or it's incorporated.

comment:12 Changed 3 years ago by mnot@pobox.com

  • Description modified (diff)

Changed 3 years ago by julian.reschke@gmx.de

proposed change for p2

comment:13 Changed 3 years ago by julian.reschke@gmx.de

From [1417]:

add considerations for new header fields (see #231)

comment:14 Changed 3 years ago by mnot@pobox.com

What else needs to be done to close this?

comment:15 Changed 3 years ago by julian.reschke@gmx.de

From [1444]:

typo (see #231)

comment:16 Changed 3 years ago by julian.reschke@gmx.de

From [1446]:

note the implications of not using the list syntax (see #231)

comment:17 Changed 3 years ago by julian.reschke@gmx.de

From [1448]:

add advice on parameter syntax (token/quoted-string) (see #231)

comment:18 Changed 3 years ago by julian.reschke@gmx.de

From [1451]:

param names are case-insensitive (see #231)

comment:19 Changed 3 years ago by julian.reschke@gmx.de

From [1458]:

Recommend header field syntax where field-recombination using "," can be detected (see #231)

comment:20 Changed 3 years ago by julian.reschke@gmx.de

See also [1463].

comment:21 Changed 3 years ago by julian.reschke@gmx.de

From [1466]:

Mark issue as done (see #231)

comment:22 Changed 3 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 17

comment:23 Changed 2 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:24 Changed 2 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed

comment:25 Changed 2 years ago by julian.reschke@gmx.de

  • Summary changed from Considerations for new headers to Considerations for new header fields
Note: See TracTickets for help on using tickets.