[BUG]: VS Code Extension API Calls Fail Due to SSL Certificate Validation

[anish-qqa]

Describe the bug

API calls from the VS Code extension fail due to SSL certificate validation errors. As a temporary workaround, disabling Strict SSL in VS Code and setting NODE_TLS_REJECT_UNAUTHORIZED=0 before launching VS Code allows the API calls to succeed.

This indicates that the extension is unable to communicate with the backend when SSL certificate validation is enabled.

Steps to reproduce

1. Install and open the PostQode VS Code extension.
2. Configure the extension with a valid server/API endpoint.
3. Attempt any API operation (e.g., login, fetch data, execute request, etc.).
4. Observe that the API request fails with an SSL/TLS related error.
5. Disable Strict SSL in VS Code.
6. Launch VS Code after setting NODE_TLS_REJECT_UNAUTHORIZED=0.
7. Repeat the same operation.

Expected behavior

The extension should successfully make API requests without requiring users to:

• Disable VS Code Strict SSL.
• Set NODE_TLS_REJECT_UNAUTHORIZED=0.

The extension should correctly validate trusted certificates or provide proper certificate handling.

Actual behavior

API requests fail with SSL certificate validation enabled.

The only known workaround is:

• Set VS Code Strict SSL to false.
• Launch VS Code with NODE_TLS_REJECT_UNAUTHORIZED=0.

After applying the workaround, API calls succeed.

Screenshots

Environment

• PostQode:
• VS Code:
• OS: Windows

Additional context

Current temporary workaround:

1. Set Strict SSL to false in VS Code Settings.
2. Close VS Code completely.
3. Open PowerShell.
4. Run: