-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Corporate Proxy results in BadCertificate Alert #20668
Comments
@kt3k do you think this one is still valid? My feeling is that it's probably stale. |
I think this is a Deno CLI issue and still valid.
The upgrade checker checks Line 451 in bb4b00d
|
Thanks for the clarification. |
@twihno, does this issue still happen when you use |
Sorry for the late reply. The log of the example with the current deno and std version (note: I just copied the example from this issue and removed the explicit std version to get the current one because I was too lazy to look up the correct version. Therefore there is a warning for the implicit std version):
|
Describe the bug
A corporate proxy with its own HTTPS certificate results in the error/alert
Sending fatal alert BadCertificate
in the command line. The proxy cert is signed by the corporate CA with the root certificate imported into the OS cert store.
(Somewhat related to #11491)
Steps to Reproduce
start.sh
test.ts
Output
Expected behavior
No error message
Additional Question
Why does Deno try to connect to https://dl.deno.land?
Environment
The text was updated successfully, but these errors were encountered: