-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Support following fetch redirect responses #626
Comments
Looks like the failing tests have been added already: #581. We may need more, but this is a good start. |
Added failing compliance tests for fetch here: #627 Confirm that Undici's fetch does follow redirect responses as described in the expected behavior. |
Released: v0.35.0 🎉This has been released in v0.35.0! Make sure to always update to the latest version ( Predictable release automation by @ossjs/release. |
There are instances where redirect responses to fetch requests aren't being followed:
fetch
mock does not follow redirect nock/nock#2755Caution
Before fixing this, we need to write compliance tests for different request modules in accordance to how they follow or don't follow redirects. Note that not all request modules may have redirect following built-in. For example, I believe the
http
module doesn't do that, thus the existence of designated third-party modules just for that functionality.Roadmap
fetch
). A good start: test: add mock redirect response tests for "axios" and "follow-redirects" #581The text was updated successfully, but these errors were encountered: