Skip to content

Conversation

jonjaques
Copy link

This fixes #91.

Was getting an issue with an API that redirects all calls from their public endpoints. Tests passing.

@jonjaques jonjaques changed the title Swap out native http(s) for follow-redirectsThis fixes #91. Swap out native http(s) for follow-redirects Feb 13, 2018
@monkpow
Copy link
Collaborator

monkpow commented Mar 15, 2018

@jonjaques I like this change, but am, also working on swapping out the underlying request mechanism for one that also follow-redirects automatically. I'm gonna put this on hold for the moment.

@jonjaques
Copy link
Author

No worries. If/when you do add redirects, holler at me so I can update ma' deps. Good luck, I appreciate this package quite a bit!

bluthen added a commit to bluthen/express-http-proxy that referenced this pull request Oct 4, 2019
@ceremonious
Copy link

Any updates on getting this merged in? Would be helpful for our project as well.

@topikuning
Copy link

Any updates on getting this merged in? Would be helpful for our project as well.

I think it's better for merge by yourself for now, since there is no change event there are update 4 month ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How to handle 301 redirects?

4 participants