New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
axios auth does not seem to be propagated on redirect in 1.15.4+ #243
Comments
That shouldn't be the case indeed! Are you sure it's not an HTTP/HTTPS redirect issue as in #192? |
Yea it shouldn't be an HTTP/HTTPS redirect issue. Both URLs for my case are HTTPS. And even so, it looks like you fixed the issue in 1.14.9 and I'm seeing a broken workflow between 1.15.3 and 1.15.4. |
Hi ! Any updates on this issue ? I'm facing the same problem with both URLs in HTTPS... |
It's on the backlog; current funds are too limited to put a dedicated person on this. I'm trying on a best-effort basis. |
I was getting the same problem with version 1.15.2 (also tryed 1.15.3 and 1.15.6) on a login request where the POST request to make the login is a redirectable request, returnin 302 status (if I disable redirects). But if the redirects are enable I'm getting a 200 responso but the login was not success. |
Yes, if you manually pass in the headers, it will work as I had originally reported (tapping into axios' beforeRedirect handler). Nevertheless, that is only a workaround and this is still a clear regression happening in 1.15.4+. As 1.15.4+ fixes vulnerability CVE-2023-26159, it would be great if this could be fixed and released such that we get a version of this library with both the vulnerability fix and no serious regression. |
I am seeing this issue as described in axios/axios#6179
This looks to be regression in 1.15.4 as it both workflows below work in 1.15.3. Whereas in 1.15.4+,
Basically this would return 401 after the redirect as the auth options don't seem to be propagated.
whereas this works and returns 200:
Through debugging, I can confirm it gets lost because the below works:
The text was updated successfully, but these errors were encountered: