27687 2014-12-23 18:45:47 +0000 Make leading/trailing whitespace and leading colons in pathnames non-conforming 2015-08-14 12:22:33 +0000 1 1 1 Unclassified WHATWG URL unspecified PC Linux RESOLVED FIXED P2 normal Unsorted 1 rubys rubys annevk julian.reschke mike rubys sideshowbarker+urlspec oldest_to_newest 116666 0 rubys 2014-12-23 18:45:47 +0000 urltestdata.txt has the following tests that don't match the production rules for valid URIs but don't produce any conformance errors. This can be fixed with two changes: A parse error if leading/trailing white space is present in: https://url.spec.whatwg.org/#concept-basic-url-parser A parse error if a colon is present in: https://url.spec.whatwg.org/#relative-path-start-state - - - The corresponding places where the rewritten parser would have to change would be: https://specs.webplatform.org/url/webspecs/develop/#concept-basic-url-parser https://specs.webplatform.org/url/webspecs/develop/#path 116675 1 rubys 2014-12-24 14:30:21 +0000 Here are the tests from urltestdata.txt: "\t :foo.com \n" " foo.com " " \t" ":foo.com/" ":" ":a" ":/" ":#" ":23" "::" "::23" Based on discussions with annevk, this should be fixed in https://specs.webplatform.org/url/webspecs/develop/#relative-url instead; in the description for row #4, add a check for the first segment containing a colon and indicating a conformance error if one is found. 116676 2 rubys 2014-12-25 00:04:20 +0000 Fixed by https://github.com/webspecs/url/commit/a6114157782a7f3d260e2a8d2e8db2e914633f3f 121215 3 rubys 2015-06-18 11:34:40 +0000 Fix was only applied to webspecs 122612 4 annevk 2015-08-14 12:22:33 +0000 Thank you. It's not entirely clear to me why a leading colon is problematic, but I've fixed the other missing parse errors and some. If you find out why a leading colon is problematic a GitHub issue would be appreciated. https://github.com/whatwg/url/commit/0bae5e5608bfc6132937f8f28388c6f796c9a846