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 Jul 30, 2018. It is now read-only.
It could be useful to store all redirecting URLs in an array e. g. in the options object.
The options are returned with the response and the user now knows the URLs "in between" request and response.
The text was updated successfully, but these errors were encountered:
It is worth investigating, in that browser caches are likely handling this automatically when a 301 or a 302 is provided. It might be totally unnecessary.
Well, it is not about handling. It is more about knowing.
For example Web-Sign In solutions like RelMeAuth or IndieAuth :
It would be useful to say until the end of the session that all these URLs redirect to target X.
That really feels like a higher order application concern. If you are in possession of a token that means you are logged in, then remapping a load of URLs is something an application can do. Worst case, the approach would be some sort of request provider that is then registered as the default provider (or even a particular set of URLs) with something like:
It could be useful to store all redirecting URLs in an array e. g. in the options object.
The options are returned with the response and the user now knows the URLs "in between" request and response.
The text was updated successfully, but these errors were encountered: