Skip to content

http: match subdomains for plain NO_PROXY entries - #65617

Open
dibenkobit wants to merge 1 commit into
nodejs:mainfrom
dibenkobit:http-no-proxy-suffix
Open

http: match subdomains for plain NO_PROXY entries#65617
dibenkobit wants to merge 1 commit into
nodejs:mainfrom
dibenkobit:http-no-proxy-suffix

Conversation

@dibenkobit

Copy link
Copy Markdown

NO_PROXY=example.com only exact-matched the hostname in the
http(s) builtins, so requests to subdomains still used the proxy.
fetch() already matches the host and its subdomains.

Reuse the existing suffix matcher (label boundary) for plain
entries as well as leading-dot ones. *.example.com is unchanged
(subdomains only, not the apex).

Fixes: #65616
Refs: #57872
Assisted-by: Grok 4.6 Extra High

cc @nodejs/http

Made with Cursor

NO_PROXY=example.com only exact-matched the hostname in the
http(s) builtins, so requests to subdomains still used the proxy.
fetch() already matches the host and its subdomains.

Reuse the existing suffix matcher (label boundary) for plain
entries as well as leading-dot ones.

Fixes: nodejs#65616
Assisted-by: Grok 4.6 Extra High
Signed-off-by: Nikita Snetkov <lukyanish@gmail.com>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/http
  • @nodejs/net

@nodejs-github-bot nodejs-github-bot added http Issues and PRs related to the http subsystem. needs-ci PRs that need a full CI run. labels Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

http Issues and PRs related to the http subsystem. needs-ci PRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NO_PROXY=example.com does not bypass subdomains for http.request(), unlike fetch()

2 participants