Looks like we need to wait until the 20th for this to be shipped. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533043/comments/8

Great, thanks for lettings us know! This is hitting us pretty badly ATM, so Im happy we now know why. :)

Great! This has hit us pretty badly, good know what is causing it.

Im afraid I cannot assist with that as I don't work for Pivotal. But CF_TRACE=true cf ssh appX.... might provide more information. <bren(a)juanantonio.info> wrote:

IIRC in recent version of the CLI a plugin for SSH is not necessary. <bren(a)juanantonio.info> wrote:

We have this in our stub. properties.uaa.scim.users: - "admin|DESIRED_PASSWORD|scim.write,scim.read....... Works well.

Very cool. Thanks for sharing!

Why, yes, yes it does. Somehow missed this feature. Thanks! //Simon

Hihi. In our environment we provide two different CF installations, each of them resides in a different VLAN. Apps in each environment are interested in different services, Graphite, statsd, sentry et

https://groups.google.com/forum/#!searchin/golang-nuts/Inconsistent$20X-Forwarded-For/golang-nuts/iUnZgzrOszI/ngxcLbSm1VYJ Mail thread about the issue at golang-nuts. This is not really a massive issu

I have now asked in golang-nuts[1] . It might take up to 24h for my message to appear, it will be called "Inconsistent X-Forwarded-For when using the httputil.ReverseProxy ?" [1] https://groups.google

Chris, I now know why this is happening. In ServeHTTP in reverseproxy in the httputil package[1] we make a copy of the incoming request for the outgoing request[2]. We then check[3] if the incoming re

Disregarding F5/HAProxy comletely and going directly(10.230.18.134) to a Gorouter also yields different results depending on the client. $ curl -H "host:cf-env.domain.com" 10.230.18.134 $ wget --heade

Dieu, We use F5, just tried with the release HAProxy and I get concictent X-Forwarded-For between clients! Dont know how I managed to forget to check that. :) So in the HAProxy config the header gets

Gist of diff: https://gist.github.com/simonjohansson/847e972f1459ea4cd65e Gist of debug output: https://gist.github.com/simonjohansson/3324b08fc42e5ac7105a Since it's quite hard to read in the email..

Hiya! Im looking into an issue where the x_forwarded_for have different values depending on what you are using to hit it with. With curl, w3m, lynx x_forwarded_for gets set to "sourceIP, a-gateway-ip"

Ah, that is interesting, thanks! Re my initial problem, turned out to be a scaling issue. Most of the CPU on the gorouters were consumed by metron agent, so adding more CPU and scaling out the routers

Gwenn, our buffer is set to 500(default is 100). wrote:

Howdie! Not really a dev related question, but since there is no cf-user list I'm trying my luck here. :) Im looking into an issue where we don't get enough RTR logs from cf logs / firehose-to-syslog

Here is a PR David and I worked on this morning to implement the above https://github.com/cloudfoundry/gorouter/pull/92 Comments are appreciated.