vscode: Certificate incorrectly recognized as expired
Issue Type: Bug
Hi,
I have a server with valid certificate - accepted by OS browser (firefox), also following code under node v14.4.0 returns status code 302:
const https = require('https');
https.get(URL, res => console.log(res.statusCode)).on('error', e => console.log(e));
But under vscode the same code gives “Error: certificate has expired”. I’ve also tried node-fetch and superagent modules, same result.
The server is not visible externally unfortunately.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z) OS version: Windows_NT x64 10.0.18363
System Info
Item | Value |
---|---|
CPUs | AMD Ryzen 7 2700X Eight-Core Processor (16 x 3693) |
GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 15.95GB (7.57GB free) |
Process Argv | |
Screen Reader | no |
VM | 0% |
Extensions (2)
Extension | Author (truncated) | Version |
---|---|---|
code-groovy | mar | 0.1.2 |
vscode-typescript-tslint-plugin | ms- | 1.2.3 |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (8 by maintainers)
Commits related to this issue
- chore: bump electron@9.3.2 Fixes https://github.com/microsoft/vscode/issues/102252 — committed to jmannanc/vscode by deepak1556 4 years ago
https://github.com/electron/electron/pull/25313 should fix this.
yeah this is pending a fix from electron, we will update as soon as fix is available. Thanks for confirming the details,