-
Notifications
You must be signed in to change notification settings - Fork 46
Revert "[ONCALL-125] chore: stop api client request to be proxied" #228
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
Merged
nsrCodes
merged 1 commit into
master
from
revert-214-stop-api-client-request-to-be-proxied
Nov 13, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🧩 Analysis chain
Verify
HttpsProxyAgentusage for HTTP traffic.Line 39 uses
HttpsProxyAgentfor thehttpAgentproperty, which handles HTTP requests. WhileHttpsProxyAgentmight support HTTP, this configuration seems unusual. Typically, HTTP and HTTPS agents are different types.Verify that
HttpsProxyAgentcorrectly handles plain HTTP requests, or consider whether a dedicated HTTP proxy agent should be used instead.🌐 Web query:
💡 Result:
HttpsProxyAgent is an http.Agent that issues an HTTP CONNECT to the proxy and is intended for proxying HTTPS (and other CONNECT-using protocols like WebSocket). It’s designed for use with Node's https module — for plain HTTP requests you should use HttpProxyAgent (or proxy-agent which selects the right agent). [1][2]
Sources:
[1] https-proxy-agent README (npm).
[2] proxy-agent README / mapping (Skypack).
Replace
HttpsProxyAgentwithHttpProxyAgentfor HTTP traffic at line 39.HttpsProxyAgent is designed for proxying HTTPS (and other CONNECT-using protocols like WebSocket). For plain HTTP requests, use
HttpProxyAgentinstead.Update line 39 from:
to:
Ensure
HttpProxyAgentis imported from thehttps-proxy-agentpackage.🤖 Prompt for AI Agents