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 }}
Repository navigation
Support net.BlockList in http.Agent options #55000
Enable users to allow or block requests when using http.request, fetch, etc.
What is the feature you are proposing to solve the problem?
Node.js already supports net.BlockList, it'd be awesome if you could simply pass in an instance of net.BlockList when creating a custom http.Agent and then have it automatically enforce the IP checks for you.
What alternatives have you considered?
I believe the only way to do this at the moment is a bit boilerplate-y, which would be using a custom lookup function that calls dns.lookup(hostname) manually, then calls blocklist.check(address) manually, and then if it flags, throw an error, else return the address.
Although that still isn't a complete solution because the lookup function isn't called for hostnames that are already IP addresses, so even more code to do the check fully :(
There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the
never-staleIssues and PRs exempt from automated stale handling.
label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
Activity
github-actions commentedon Mar 19, 2025
There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-staleIssues and PRs exempt from automated stale handling.
label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
github-actions commentedon Apr 18, 2025
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
For more information on how the project manages feature requests, please consult the feature request management document.