httpbis: Ticket #67: Quoting Charsets
Link: http://trac.tools.ietf.org/wg/httpbis/trac/ticket/67
Origin:
http://www.w3.org/mid/OF0F79F4C4.48F60CCC-ONC12572E4.004020CE-C12572E4.00403138@de.ibm.com
Component:
p3-payload
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.
Mails
Associated Checkins
- julian.reschke@gmx.de
(Wed, 28 May 2008 14:55:30 GMT)
-
[250]:
Improve alignment in BNF (related to #67)
- julian.reschke@gmx.de
(Fri, 30 May 2008 09:52:37 GMT)
-
[251]:
Resolve #67: media-range: token and quoted-string notation for parameters ...
- fielding@gbiv.com
(Wed, 30 Jul 2008 04:15:43 GMT)
-
[251]:
Resolve #67: media-range: token and quoted-string notation for parameters ...
- julian.reschke@gmx.de
(Wed, 30 Jul 2008 06:45:22 GMT)
-
[297]:
Resolve #67: Adopt rephrasing of the statement proposed by Roy (closes ...
History
: comment added (Sat, 22 Dec 2007 02:53:41 GMT)
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 added; component, milestone set (Fri, 04 Jan 2008 06:05:40 GMT)
-
component
set to messaging
-
milestone
set to unassigned
: comment added; owner set; status, milestone changed (Sat, 05 Jan 2008 01:53:54 GMT)
-
owner
set to fielding@gbiv.com
-
status
changed from new to assigned.
-
milestone
changed from unassigned to 02.
: comment added; type changed (Tue, 05 Feb 2008 01:38:02 GMT)
-
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 added; milestone changed (Thu, 28 Feb 2008 05:26:57 GMT)
-
milestone
changed from 02 to 03.
: comment added; milestone changed (Wed, 02 Apr 2008 06:00:44 GMT)
-
milestone
changed from 03 to unassigned.
: comment added (Fri, 09 May 2008 06:05:02 GMT)
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 added; milestone changed (Mon, 26 May 2008 11:42:08 GMT)
-
milestone
changed from unassigned to 03.
Proposal accepted.
: comment added (Wed, 28 May 2008 14:55:30 GMT)
From [250]:
Improve alignment in BNF (related to #67)
: comment added; owner, status, component changed (Wed, 28 May 2008 15:46:03 GMT)
-
owner
changed from fielding@gbiv.com to julian.reschke@gmx.de
-
status
changed from assigned to new.
-
component
changed from p1-messaging to p3-payload.
: comment added; attachment set (Thu, 29 May 2008 15:50:47 GMT)
-
attachment
set to i67.diff
proposed change for part 3
: comment added; resolution set; status changed (Fri, 30 May 2008 09:52:37 GMT)
-
status
changed from new to closed.
-
resolution
set to fixed
Fixed in [251]:
Resolve #67: media-range: token and quoted-string notation for parameters is equivalent (closes #67).
: comment added; attachment set (Wed, 30 Jul 2008 04:13:02 GMT)
-
attachment
set to i67-roy.diff
Rephrase to focus on parameter values, not parameters.
: resolution deleted; comment added; status changed (Wed, 30 Jul 2008 04:15:43 GMT)
-
status
changed from closed to reopened.
-
resolution
deleted
The change in [251] incorrectly refers to parameters instead of
parameter values. I have rephrased it in the second attachment.
: comment added; resolution set; status changed (Wed, 30 Jul 2008 06:45:22 GMT)
-
status
changed from reopened to closed.
-
resolution
set to fixed
Fixed in [297]:
Resolve #67: Adopt rephrasing of the statement proposed by Roy (closes #67).
Related Information
Issues List Index