http to https redirect breaks custom agent #6

Open
opened 3 years ago by f0x · 0 comments
f0x commented 3 years ago

With a single custom agent, it can either support http or https, and thus throws Unhandled rejection TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:" when redirecting to the other protocol.

got solves this by allowing an agent object, with http and https entries so you can provide both

With a single custom `agent`, it can either support http or https, and thus throws `Unhandled rejection TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"` when redirecting to the other protocol. [got](https://github.com/sindresorhus/got) solves this by allowing an agent object, with http and https entries so you can provide both
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: joepie91/node-bhttp#6
Loading…
There is no content yet.