-
Notifications
You must be signed in to change notification settings - Fork 16.9k
feat: add bypassCustomProtocolHandlers option to net.request #47331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💖 Thanks for opening this pull request! 💖 Semantic PR titlesWe use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of commit messages with semantic prefixes:
Commit signingThis repo enforces commit signatures for all incoming PRs. PR tipsThings that will help get your PR across the finish line:
We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. |
erickzhao
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
samuelmaddock
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
deepak1556
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@udbmnm can you rebase the PR on latest main, thanks!
c060c1f to
503c278
Compare
Done |
503c278 to
b78dd90
Compare
|
@udbmnm can you sign your commits? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits. We require signed commits. |
1f0196f to
b78dd90
Compare
b78dd90 to
e9c0e32
Compare
Done |
|
Congrats on merging your first pull request! 🎉🎉🎉 |
|
Release Notes Persisted
|
|
I have automatically backported this PR to "38-x-y", please check out #48881 |
|
I have automatically backported this PR to "39-x-y", please check out #48882 |
|
I have automatically backported this PR to "40-x-y", please check out #48883 |
…n#47331) * feat: add bypassCustomProtocolHandlers option to net.request * style: fix lint errors in api-protocol-spec
…n#47331) * feat: add bypassCustomProtocolHandlers option to net.request * style: fix lint errors in api-protocol-spec
…n#47331) * feat: add bypassCustomProtocolHandlers option to net.request * style: fix lint errors in api-protocol-spec
Description of Change
This PR adds the
bypassCustomProtocolHandlersoption tonet.request(), making it consistent withnet.fetch()which already has this parameter.Currently, when using custom protocol handlers registered via
protocol.handle(), there's a potential issue with circular interception when a handler needs to make network requests. Whilenet.fetch()provides thebypassCustomProtocolHandlersparameter to prevent this,net.request()(which is used internally bynet.fetch()) doesn't expose this option directly.Close #47098
Checklist
npm testpassesRelease Notes
Notes: Add bypassCustomProtocolHandlers option to net.request