This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26550 - Definition of "valid MIME type" still refers to RFC 2616
Summary: Definition of "valid MIME type" still refers to RFC 2616
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-10 19:50 UTC by Spencer Harris
Modified: 2014-08-28 15:10 UTC (History)
2 users (show)

See Also:

Attachments

Description Spencer Harris 2014-08-10 19:50:48 UTC 
Section 2.1.1 "Resources" states:

A string is a valid MIME type if it matches the media-type rule defined in section 3.7 "Media Types" of RFC 2616.
...
A string is a valid MIME type with no parameters if it matches the media-type rule defined in section 3.7 "Media Types" of RFC 2616

However, RFC 2616 is obsolete and is no longer listed as a normative reference. It should probably be changed to refer to section 3.1.1 "Processing Representation Data" of RFC 7231.
Comment 1 Robin Berjon 2014-08-28 15:10:41 UTC 
Fixed, thanks!