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
…onse
Handle set-cookie from a redirect response fixes#13
use `URL::hostname` instead of `URL::host` according to RFC ports don't matter
improve tests
prevent leaking sensitive headers to other domains after redirect
Seems like we need to handle cookies that are set when the response is
301, 302, 303, 307, 308
.e.g. 302 responses can contain
response.headers.set-cookie
that we need to store.To implement it
fetch
needs to handle redirects manually:... and check if it is a redirect status in
response.status
, then if it's a redirect; recursively call it self with something like.We also need to add a
maxRedirect
option to check against a counter to avoid redirect loops.I don't have the time to finish this now, but started a draft that i think will work. Maybe someone will pick it up :-)
The text was updated successfully, but these errors were encountered: