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 13354 - Willful violation of HTTP
Summary: Willful violation of HTTP
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2011-07-25 17:37 UTC by Mark Nottingham
Modified: 2011-09-23 19:48 UTC (History)
5 users (show)

See Also:


Description Mark Nottingham 2011-07-25 17:37:20 UTC
In <>, it says:

Note: This algorithm is a willful violation of the HTTP specification, which requires that the encoding be assumed to be ISO-8859-1 in the absence of a character encoding declaration to the contrary, and of RFC 2046, which requires that the encoding be assumed to be US-ASCII in the absence of a character encoding declaration to the contrary. This specification's third approach is motivated by a desire to be maximally compatible with legacy content. [HTTP] [RFC2046]

It would be more helpful to say that it's a willful violation of RFC2616, but HTTPbis is changing HTTP to allow this.
Comment 1 Michael[tm] Smith 2011-08-04 05:04:54 UTC
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-11 21:53:46 UTC
Do you have a link to the new requirements? I'm happy to remove the note and just reference the new HTTP spec if it's indeed fixing this.
Comment 3 Mark Nottingham 2011-08-12 00:35:24 UTC

The default encoding in RFC2046 is a known issue, and will be addressed by:
...which is becoming a work item of the APPSAWG:
Comment 4 Ian 'Hixie' Hickson 2011-09-21 19:55:40 UTC
Ok, I'll comment out the paragraph.
Comment 5 Ian 'Hixie' Hickson 2011-09-23 19:45:29 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Accepted
Change Description: see diff given below
Rationale: see comment 4
Comment 6 contributor 2011-09-23 19:48:55 UTC
Checked in as WHATWG revision r6575.
Check-in comment: Comment out a 'willful violation' that is being fixed in the underlying specs.