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
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
It appears that I introduced a slight behavior change in d6bbb19, where previously a custom http.Agent instance would not be required to have its own protocol field, now it is mandatory.
This ends up being a problem for custom-defined http.Agent instances that don't necessarily subclass from the core http.Agent class, like my agent-base module.
It appears that I introduced a slight behavior change in d6bbb19, where previously a custom
http.Agent
instance would not be required to have its ownprotocol
field, now it is mandatory.This ends up being a problem for custom-defined
http.Agent
instances that don't necessarily subclass from the corehttp.Agent
class, like myagent-base
module.First reported in TooTallNate/node-proxy-agent#1. I'll have a patch ready shortly.
The text was updated successfully, but these errors were encountered: