Bug 191 – Content-Type parsing should stop on a semicolon.

NOTE: The current preferred location for bug reports is the GitHub issue tracker.

Bug 191 - Content-Type parsing should stop on a semicolon.


Summary:	Content-Type parsing should stop on a semicolon.

Status:	RESOLVED FIXED

Product:	Validator.nu
Classification:	Unclassified
Component:	HTML parser
Version:	HEAD
Hardware:	All All

Importance:	P2 normal
Assigned To:	Henri Sivonen

URL:	http://svn.whatwg.org/webapps/source?...

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-05-22 14:15 CEST by Henri Sivonen
Modified:	2008-05-31 16:30 CEST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Henri Sivonen 2008-05-22 14:15:54 CEST

Index: source
===================================================================
--- source	(revision 1664)
+++ source	(revision 1665)
@@ -31563,6 +31563,8 @@
 
    <li><p>If the next seven characters are not a case-insensitive<!--
    XXX ASCII--> match for 'charset', return nothing.</p></li>
+   <!-- XXX technically, we should skip to the next MIME parameter,
+   but the question is, do browsers do that? -->
 
    <li><p>Skip any U+0009, U+000A, U+000B, U+000C, U+000D, or U+0020
    characters that immediately follow the word 'charset' (there might
@@ -31596,8 +31598,8 @@
      <dt>Otherwise</dt>
 
      <dd><p>Return the string from this character to the first U+0009,
-     U+000A, U+000B, U+000C, U+000D, or U+0020 character or the end of
-     <var title="">s</var>, whichever comes first.</dd>
+     U+000A, U+000B, U+000C, U+000D, U+0020, or U+003B character or
+     the end of <var title="">s</var>, whichever comes first.</dd>
 
     </dl>