HTTP Basic Auth
Nate Sutton <[email protected]> Thu, 16 May 2019 12:57:27 -0500
| Newsgroups | gmane.network.lftp.user |
|---|---|
| Message-ID | <CAMZDCY24zvEzzoWw1=55bjX4uo16DaCeEzs4N6bkXgD+A6WMkg@mail.gmail.com> |
--===============5246536360905806600== Content-Type: multipart/alternative; boundary="0000000000006ddeb405890500ed" --0000000000006ddeb405890500ed Content-Type: text/plain; charset="UTF-8" Something changed between lftp 4.4.8 and lftp 4.8.4 with HTTP basic auth. In the newer version it only sends the Authorization header if it receives a challenge response from making a request without the header. In the older version it always sent the Authorization header. Is there a way to force sending the Authorization header on the first request? Not all endpoints that accept HTTP basic auth respond with a challenge, some redirect to oauth or whatever else. Thanks! --0000000000006ddeb405890500ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Something changed between lftp 4.4.8 and lftp 4.8.4 with H= TTP basic auth. In the newer version it only sends the Authorization header= if it receives a challenge response from making a request without the head= er. In the older version it always sent the Authorization header.<div><br><= /div><div>Is there a way to force sending the Authorization header on the f= irst request? Not all endpoints that accept HTTP basic auth respond with a = challenge, some redirect to oauth or whatever else.</div><div><br></div><di= v>Thanks!</div></div> --0000000000006ddeb405890500ed-- --===============5246536360905806600== 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 --===============5246536360905806600==--