See network requests made by extensions in network tab of developer tools

[nicksnyder]

This would be useful to me both as a user (to see what extension are doing) and as a developer (to debug extensions).

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[bestkanthed]

I would want the same

[itsdarrylnorris]

Same here.

[thakkarparth007]

+1

[Fernando-Abreu]

+1

[zutshisunakshi]

I don't see any requests/response coming in network tab now, did anything change?

[tinkerology]

This really would be super helpful, especially for debugging extensions.

[aryamankha]

+1

[supuwoerc]

+1

[RichardoC]

For anyone trying to do this, vscode doesn't support this but you can use a Man-In-The-Middle (MITM) proxy to capture all traffic from VScode, including from extensions.

Warning, this will capture all API calls including API tokens, and effectively disable HTTPS verfication so only use if you know what you're doing

Steps

• Install Zap
• Start ZAP, it'll set up a proxy running on http://localhost:8080
• Configure VScode to use this proxy by setting the following settings
  • "http.proxy": "http://localhost:8080"
  • "http.proxyStrictSSL": false
  • "http.proxySupport": "override"
• Now close Vscode, and reopen it from a terminal with code --ignore-certificate-errors
• Inspect the traffic by following the quick start guide for ZAP

Why disable all these security features?

• VScode will not trust the ZAP CA, even if it's added to the system certificate chain due to extensions ignoring some settings so we have to disable verification

When finished

• Delete "http.proxy" setting
• Close VScode
• Reopen VS code normally