Skip to content

fix(fetch): preserve port when matching noProxy patterns (#13366) - #13385

Open
patrickswedish wants to merge 1 commit into
continuedev:mainfrom
patrickswedish:fix/fetch-noproxy-port-matching-13366
Open

patrickswedish wants to merge 1 commit into
continuedev:mainfrom
patrickswedish:fix/fetch-noproxy-port-matching-13366

Conversation

@patrickswedish

Copy link
Copy Markdown

Summary

Preserves the URL port during noProxy evaluation in fetchwithRequestOptions so port-specific proxy bypass rules (such as 127.0.0.1:11434 or localhost:11434) correctly match and bypass the configured proxy.

Changes

  • In packages/fetch/src/fetch.ts, normalize url.hostname (preserving any port on url.host) and pass url.host (and originalHost) to shouldBypassProxy.
  • In packages/fetch/src/util.test.ts, add unit tests verifying port discrimination for IP and localhost noProxy rules.

Fixes #13366


Diff minimization and pre-flight validation performed with ZeroSlop™ CI — Ribbsaeter Systems.

@patrickswedish
patrickswedish requested a review from a team as a code owner October 15, 2026 21:30
@patrickswedish
patrickswedish requested review from sestinj and removed request for a team October 15, 2026 21:30
@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

…#13366)

Signed-off-by: Patrick Ribbsaeter <patrickswedish@gmail.com>
@patrickswedish
patrickswedish force-pushed the fix/fetch-noproxy-port-matching-13366 branch from 5887011 to f5cf295 Compare October 15, 2026 21:44

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Port-specific noProxy entries do not bypass the proxy

1 participant