gcf logs not respecting proxy servers about cli HOT 7 CLOSED

Hi Jon,

We'll either get this when the go.net websocket library supports proxies or we'll have to ask Loggregator to support another protocol. I'll loop back with you when we have a better idea which way this is going.

Scott

from cli.

Jon, will you please give us more detail on how you're using a proxy?

from cli.

Hi Scott,

We also submitted an issue for the websocket library itself at https://code.google.com/p/go/issues/detail?id=7182

All of our users will be working from within a corporate Intranet and have to access the CF deployment through our proxy servers. They set the http_proxy and https_proxy environment variables at the command line. The are just standard http proxies and unfortunately are not transparent.

At present, we are unable to have our users use gcf due to issue #29 and this loggregator problem. :(

Jon

from cli.

I have #29 near the top of my backlog next week. Apologies for the delay, we're finally ready to take care of it.

I've forwarded this issue to the Loggregator PM.

from cli.

@jmprice please have a look at our latest release: https://github.com/cloudfoundry/cli/releases/tag/v6.1.1

v6.1.1 contains a PR from the community to that should make loggregator functional for you. Both tail and --recent. Please let me know.

from cli.

Hi Scott - It works! :)

Thank you very much for all your work getting this working. Now the only thing we have blocking us is the LDAP login issue.

Jon

from cli.

Thanks, Jon. That's the next story in the backlog.

On Thu, Apr 24, 2014 at 11:02 AM, Jon Price [email protected]:

Hi Scott - It works! :)

Thank you very much for all your work getting this working. Now the only
thing we have blocking us is the LDAP login issue.

Jon

Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-41312290
.

from cli.