-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix: fix ci with cert issue #11462
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
Closed
Closed
fix: fix ci with cert issue #11462
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.
Check failure
Code scanning / CodeQL
Disabling certificate validation High
Copilot Autofix
AI 1 day ago
In general, the problem is that TLS certificate validation is disabled by setting
rejectUnauthorized: falsein the customhttps.Agentused by Axios. The fix is to avoid disabling validation: either use the defaulthttps.Agent(no customhttpsAgentconfiguration at all), or explicitly setrejectUnauthorized: true. If special handling of self‑signed certificates is needed, it should be done via trusted CA configuration instead, not by turning validation off.The minimal, non‑breaking change here is to stop passing
rejectUnauthorized: falsewhen constructing the agent. Since Node’s default HTTPS agent already enforces certificate validation, the cleanest approach is to remove the customhttpsAgententirely and let Axios use its default. That preserves all existing behavior except for making TLS secure again. Concretely, inpackages/http-caching-proxy/src/http-caching-proxy.ts, within theHttpCachingProxyconstructor, we should delete thehttpsAgentproperty (lines 92–96 in the snippet) and the associated comment about disabling SSL validation. No new imports are needed, because we will no longer userequire('node:https')here. Axios will automatically use Node’s standard HTTPS handling, which validates certificates.