13354 2011-07-25 17:37:20 +0000 Willful violation of HTTP 2011-09-23 19:48:55 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED P2 normal --- 1 mnot ian ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51447 0 mnot 2011-07-25 17:37:20 +0000 In <http://www.w3.org/TR/html5/parsing.html#determining-the-character-encoding>, 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. 52861 1 mike 2011-08-04 05:04:54 +0000 mass-moved component to LC1 54734 2 ian 2011-08-11 21:53:46 +0000 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. 54756 3 mnot 2011-08-12 00:35:24 +0000 See: http://trac.tools.ietf.org/wg/httpbis/trac/ticket/20 and: http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/20/i20.2.diff The default encoding in RFC2046 is a known issue, and will be addressed by: http://tools.ietf.org/html/draft-melnikov-mime-default-charset ...which is becoming a work item of the APPSAWG: http://www.ietf.org/proceedings/81/minutes/appsawg.txt 57096 4 ian 2011-09-21 19:55:40 +0000 Ok, I'll comment out the paragraph. 57259 5 ian 2011-09-23 19:45:29 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: see comment 4 57262 6 contributor 2011-09-23 19:48:55 +0000 Checked in as WHATWG revision r6575. Check-in comment: Comment out a 'willful violation' that is being fixed in the underlying specs. http://html5.org/tools/web-apps-tracker?from=6574&to=6575