HTTPS Proxies
Squidly271 opened this issue · 1 comments
I've never had to use a proxy, but I've been working with a guy and its necessary for him to use.
Much of the GUI utilizes wget which will pick up the proxy environments set up in "go" if necessary. However much of the GUI now uses CURL, which does not use the environments, and the additional curl options are required.
Now, I was going to toss into CA's settings a proxy option for it's curl (I've tested the coding to see what he needed), but that doesn't solve the other notable inclusion of curl in the GUI. The entire docker system. What should we do about those potential users who do require a proxy to be set up?
Closing. Tested with a specific user, and the issue can be handled via CA and a special config file.