You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2018. It is now read-only.
Currently, redirection is automatic. It's sometimes useful to be able to examine the intermediate response.
Per the conversation in #26, I think it should be solved like this:
Create a new subclass of OrphanHALNavigator for redirections. It will have one additional method redirect that returns the fully functional HALNavigator that is usually produced by the redirection (except that it will also fetch the resource to avoid turning this into a 3 step process)
Add a flag keyword arg to POST/PUT/PATCH/DELETE operations similar to the request library's allow_redirects flag. Instead of performing the redirect automatically, it will produce one of these RedirectionOrphans
The text was updated successfully, but these errors were encountered:
Currently, redirection is automatic. It's sometimes useful to be able to examine the intermediate response.
Per the conversation in #26, I think it should be solved like this:
OrphanHALNavigator
for redirections. It will have one additional methodredirect
that returns the fully functionalHALNavigator
that is usually produced by the redirection (except that it will also fetch the resource to avoid turning this into a 3 step process)RedirectionOrphans
The text was updated successfully, but these errors were encountered: