gcf logs hardcoded to secure websockets on port 4443 regardless of logging_endpoint about cli HOT 4 CLOSED

Thanks, Matt. We have a story to address this in our backlog: https://www.pivotaltracker.com/story/show/56811672 I expect that to be done in the next few weeks, and I'll close this issue when it is.

Scott

from cli.

I also observe that cf logs does not seem to honor the http_proxy and https_proxy (at least on windows):

c:\code>gcf logs myapp
FAILED
websocket.Dial wss://loggregator.run.pivotal.io:4443/tail/?app=005e78a9-e259-4c93-9b00-256823a1a6a8: dial tcp: GetAddrI
foW: No such host is known.

c:\code>set
[...]
https_proxy=http://127.0.0.1:3128
http_proxy=http://127.0.0.1:3128

from cli.

It looks like the lack of proxy support is because the Google golang websocket client doesn't support proxies yet. This needs to get added to the Google library then gcf can take advantage of it.

from cli.

Just accepted the fix.

from cli.