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
Agent.prototype.addRequest() in the _http_agent.jschecks for a Legacy API with a string type of the options parameter. However, this method called only with this call chain:
There are some agent subclasses using this today. Despite the addRequest function being undocumented internal API, it's easy enough to just support the old signature for backwards compatibility.
Agent.prototype.addRequest()
in the_http_agent.js
checks for a Legacy API with a string type of theoptions
parameter. However, this method called only with this call chain:http.request()
inhttp.js
->exports.ClientRequest()
in_http_client.js
->Agent.prototype.addRequest()
in the_http_agent.js
.On the
ClientRequest()
stage any string is converted to Object.Is there any reason to keep this Legacy API check in the
Agent.prototype.addRequest()
? Is this function called from a userland or in any other way?The text was updated successfully, but these errors were encountered: