Follow-up Comment #3, bug #58354 (project wget):
Note that the browser's The WHATWG URL Spec (TWUS) allows that kind of
abomination, while RFC 3986 explicitly requires two slashes to be there.
(Listed in my "URL interop" page at
https://github.com/bagder/docs/blob/master/URL-interop.md)
In fact, TWUS allows an unlimited amount of slashes (and backslashes) to be
present and is still fine with it.
Because browsers allow this, instances of such URLs appear in the wild so it
makes sense to be somewhat accommodating.
In the curl project (which primarily has RFC3986 as guidance), we've still
decided to accept one, two or three slashes as we've seen both one and three
happen in the wild. I don't believe in being more lenient than so.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58354>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
