Redirect Bug
Nate Sutton <[email protected]> Thu, 10 Oct 2019 15:17:56 -0500
| Newsgroups | gmane.network.lftp.user |
|---|---|
| Message-ID | <CAMZDCY158MEyTkvmhyU5N3V+X=4M8rKi39h0G4KtoXH-MvrZww@mail.gmail.com> |
--===============0280536238649152683== Content-Type: multipart/alternative; boundary="000000000000764d8505949419a1" --000000000000764d8505949419a1 Content-Type: text/plain; charset="UTF-8" Hi there, I think I've found a small bug in the latest lftp. When I run `pget -n 5 ' https://example.com/foo'` and it gets redirected with a Location header '/bar/baz' then the URL becomes 'https://example.com//bar/baz' -- notice the double slash? Seems like a bug? --000000000000764d8505949419a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi there,<div><br></div><div>I think I've found a smal= l bug in the latest lftp. When I run `pget -n 5 '<a href=3D"https://exa= mple.com/foo'`">https://example.com/foo'`</a> and it gets redirecte= d with a Location header '/bar/baz' then the URL becomes '<a hr= ef=3D"https://example.com//bar/baz">https://example.com//bar/baz</a>' -= - notice the double slash? Seems like a bug?</div><div><br></div></div> --000000000000764d8505949419a1-- --===============0280536238649152683== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lftp mailing list [email protected] http://univ.uniyar.ac.ru/mailman/listinfo/lftp --===============0280536238649152683==--