Opened 10 years ago

Closed 9 years ago

#67 closed design (fixed)

Quoting Charsets

Reported by: mnot@… Owned by: julian.reschke@…
Priority: Milestone: 03
Component: p3-payload Severity:
Keywords: Cc:

Description

The BNF definition of the "Content-Type" production does not utiilize the "charset" production defined in section 3.4, and therefore an occasional reader of RFC2616 who follows the BNF dependencies, does not necessarily notice section 3.4 and hence arrives at the conclusion that the quoted and unquoted form are both equally ok.

Attachments (2)

i67.diff (3.9 KB) - added by julian.reschke@… 9 years ago.
proposed change for part 3
i67-roy.diff (625 bytes) - added by fielding@… 9 years ago.
Rephrase to focus on parameter values, not parameters.

Download all attachments as: .zip

Change History (15)

comment:1 Changed 10 years ago by mnot@…

I suggest to fix this by utilizing the "charset" production somewhere in the "Content-Type" production. Maybe at the level of "media-type". In addition, an explicit reference to section 3.4 could be added to the description of Content-Type in section 14.17.

comment:2 Changed 10 years ago by mnot@…

  • Component set to messaging
  • Milestone set to unassigned

comment:3 Changed 10 years ago by fielding@…

  • Milestone changed from unassigned to 02
  • Owner set to fielding@…
  • Status changed from new to assigned

comment:4 Changed 10 years ago by fielding@…

  • Type changed from editorial to design

There is some confusion here. First, HTTP allows both quoted and unquoted forms in Content-Type, and that certainly isn't going to change. However, HTTP only uses the charset ABNF production in Accept-Charset, and thus is currently defined to only allow tokens in Accept-Charset.

Should Accept-Charset allow charset quoted strings? I don't think so. Should the charset production be removed to reduce the confusion? Perhaps. This is really a design issue.

This would be a lot easier if IANA kept a decent registry for charset that only included the "MIME preferred names". We may need to request that in the IANA considerations.

comment:5 Changed 10 years ago by mnot@…

  • Milestone changed from 02 to 03

comment:6 Changed 9 years ago by mnot@…

  • Milestone changed from 03 to unassigned

comment:7 Changed 9 years ago by mnot@…

Proposal:

  • leave accept-charset as-is.
  • explicitly allow all media-type parameters defined as a token to occur as a quoted-string, and make them equivalent (p2 section 3.3).

comment:8 Changed 9 years ago by mnot@…

  • Milestone changed from unassigned to 03

Proposal accepted.

comment:9 Changed 9 years ago by julian.reschke@…

From [250]:

Improve alignment in BNF (related to #67)

comment:10 Changed 9 years ago by julian.reschke@…

  • Component changed from p1-messaging to p3-payload
  • Owner changed from fielding@… to julian.reschke@…
  • Status changed from assigned to new

Changed 9 years ago by julian.reschke@…

proposed change for part 3

comment:11 Changed 9 years ago by julian.reschke@…

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

Fixed in [251]:

Resolve #67: media-range: token and quoted-string notation for parameters is equivalent (closes #67).

Changed 9 years ago by fielding@…

Rephrase to focus on parameter values, not parameters.

comment:12 Changed 9 years ago by fielding@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

The change in [251] incorrectly refers to parameters instead of parameter values. I have rephrased it in the second attachment.

comment:13 Changed 9 years ago by julian.reschke@…

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

Fixed in [297]:

Resolve #67: Adopt rephrasing of the statement proposed by Roy (closes #67).

Note: See TracTickets for help on using tickets.