GistPad not fully functionnal when used via authenticated proxy

[mponton]

When using GistPad on an enterprise network that requires an authenticated proxy connection, GistPad will properly login (with token) and load the list of my Gist but will not display them.

E.g. list:

But attempting to load example.ps1 fails with this error in the console:

Curiously most of the time I only get the loading indicator without any error, like if the request was sent WITHOUT going thru the proxy.

VS Code works properly, will update and download extensions via proxy etc.

[lostintangent]

Out of curiosity: have you set any VS Code settings to specify your proxy? I’m just wondering if I should be respecting them.

[mponton]

I don't anymore. The newest versions of VS Code (not sure when it started because I have this setup only since I migrated to a new PC in January) support usage of the system proxy + Windows auth via Chromium now it seems (like Chrome does; so things work out of the box). Doing more tests today, GistPad will either fail and display the above error or simply hang loading a Gist (loading bar is shown, no error, nothing loads). Yet curiously, the Gist browsing UI works fine, it's when loading an actual Gist file that it fails.

I tried setting my proxy info explicitly and the results appear to be the same.

Let me know if I can further help with this.