-
Notifications
You must be signed in to change notification settings - Fork 195
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
3xx status appear as failure? #39
Comments
+1, main problem is 304 |
How could we handle such a redirect.. can If this can be improved in a PR, i'd like to merge in the upcoming 2.0 release. |
I believe this comes from the use of redux-api-middleware/src/middleware.js Lines 147 to 159 in cbf0553
If we make this configurable, this middleware should be able to support use cases like this one. |
This is being looked at in #171 |
In 2.x, you can now pass a custom I think this should be enough to handle most situations, so I'm going to close this out. Feel free to re-open or continue commenting here though. |
After browsing through the repo, unless I'm mistaken, it appears as though any server response above 299 will be treated as an error. What about redirects ie. (responses with status codes in the 3xx range)?
It think it's a bit awkward to treat a simple redirect as an error, though some clients might want to do that, I can't see all of them wanting to do that.
The text was updated successfully, but these errors were encountered: