Skip to content

Conversation

@chinesedfan
Copy link
Contributor

@chinesedfan chinesedfan commented Jan 25, 2020

Preparation for #1804. Closed #2691.

follow-redirects was locked to 1.5.10 in #1993 and was reverted unintentionally in #1816. And #2570 locked it again.

The reason is that from follow-redirects@1.6.0, the request will be aborted when redirecting. See follow-redirects/follow-redirects@7a0a683. Then axios can't emit the error, which results in test case "should support max redirects" failed.

@RubenVerborgh
Copy link

Thanks for unpinning (see also #2691).

@RubenVerborgh
Copy link

The error message might not necessarily be a constant though; let's think of a contract that we can sustain. Such as an error code or so.

@chinesedfan
Copy link
Contributor Author

@RubenVerborgh Yeah, waiting for your good news about the error code.

@RubenVerborgh
Copy link

@chinesedfan As as of follow-redirects@1.10.0, you can check for err.code !== 'ERR_FR_TOO_MANY_REDIRECTS'.

@chinesedfan
Copy link
Contributor Author

@RubenVerborgh Updated with the error code. Thanks for your quick response.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unexpected memory usage Let's establish a closer relation with follow-redirects

3 participants