Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Redirect history #72

Open
stevenvachon opened this issue Feb 25, 2017 · 2 comments
Open

Redirect history #72

stevenvachon opened this issue Feb 25, 2017 · 2 comments

Comments

@stevenvachon
Copy link

Is it not accessible via the use of fetch's {redirect:'manual'}?
@jhiesey
Copy link
Owner

jhiesey commented Mar 20, 2017

Yes, this should be possible. I will look into adding this feature in the near future.

@jhiesey
Copy link
Owner

jhiesey commented Apr 4, 2017

OK, so reading the fetch spec it looks like responses corresponding to redirects have type "opaqueredirect", which hides the status code, message, headers, and body.

This will break things that actually expect these things in node, like request's redirection logic. So just adding support for manual redirects won't really do the right thing.

What's the right thing to do? Should stream-http give redirects a fake 3xx status code?

@jimmywarting jimmywarting mentioned this issue Oct 14, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stevenvachon @jhiesey