On Mon, 9 May 2016, Alex Bligh wrote:

> Meh. OK well that changes things a bit. If there is a WG excuse^Wrationale
> for it, if it's applied consistently, and if it doesn't break things, I
> think I'd go with it.

The rationale is not clear: The WHATWG spec allows an unlimited amount of
slashes because "all browsers do". And all browsers (presumably) do what the
spec says.

It isn't consistent either; not all browsers accept unlimited amounts of
slashes (for example when tested the other day, Safari rejected ten slashes in
a Location: redirect). Not to mention all other non-browser tools and
libraries that like us, haven't adopted the WHATWG spec.

... but then again, servers are obviously sending responses that are handled
fine by browsers and some of those responses find themselves also received by
curl and here we are! =)

A slipperly slope.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:  https://curl.haxx.se/mail/etiquette.html