--- Comment #2 from Conrad Meyer <> ---
Your fix looks correct to me.

Technically this is a non-compliant server, right?  IIRC, modern HTTP does not
allow duplicate instances of headers.  So it would also be valid for libfetch
to just reject the connection when encountering the second Location.  No?

This case is only encountered when one HTTP response contains two location
headers and not by, e.g., 302 / Location: foo => 302 / Location: bar => ...

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to