Unable to load schema from <schema path> with a transparent TLS intercepting proxy

[JonTheNiceGuy]

Describe the bug

When opening an Ansible Vars file, I get the notification: Unable to load schema from 'https://raw.githubusercontent.com/ansible-community/schemas/main/f/ansible-vars.json': No content.

I am using VSCode with WSL 2, and my Windows machine has a transparent TLS inspecting proxy. I am able to run curl and wget to these URLs within the WSL environment (as I have loaded the TLS MITM certificate).

Expected Behavior

No notification about schema loading failures.

Current Behavior

When opening an Ansible Vars file, I get the notification: Unable to load schema from 'https://raw.githubusercontent.com/ansible-community/schemas/main/f/ansible-vars.json': No content.

Steps to Reproduce

Unsure! I suspect one validation would be to install MITMProxy on another machine, set this as the gateway for all outbound traffic, and then use something like IPTables to rewrite any inbound HTTP or HTTPS packets to MITMProxy... then copy the MITMProxy CA Certificate to the certificate store. I've written up some notes on putting certificates into the certificate store here: https://jon.sprig.gs/blog/post/2150 Test it with a check using curl https://github.com and make sure that works, and then test this!

Environment

• [ ] Windows
• [ ] Mac
• [ ] Linux
• [X] other (please specify)

WSL2 Ubuntu on Windows 10

[ssbarnea]

I doubt this is problem with yaml extension, likely any https request from vscode will also be affected.