Hi Amit, This does not seem to be a port issue on 6968. I tried the same deployment by modifying the security groups (both bosh and cf ) to allow All Protocol All Ports. even wit this change the

Just to clarify as well why I think this is so important - a majority of apps on our internal platforms require authentication and will return a 401 on the root page, making them unusable on Diego for

I agree with your root argument that the port check doesn't really address application health and it's easy to push a non-working app and have the healthcheck still pass. My argument is that is

I updated the RFC pointed at in Danny's email, but figured I'd reply here as well, in the spirit of overcommunication. I'll state my opinion as the Buildpacks PMC Lead: I think we should sunset HHVM

CVE-2016-0732 Privilege EscalationSeverity Critical Vendor Cloud Foundry Foundation Versions Affected Cloud Foundry v208 through v229 UAA v2.0.0 - v2.7.3 & v3.0.0 UAA-Release v2 through

Hi, I have a question regarding the configuration of cloud controller. It is described at http://docs.cloudfoundry.org/deploying/aws/cf-stub.html#editing that DROPLET_DIRECTORY_KEY should be

In talking with a former team member, I came across the story [1] where we made this change. The WebAppServer will listen on the port immediately upon starting, even if the app has not successfully

Hey Aaron - You're right; it looks like the port check is only ever used. I don't have the history as to why we (the CF .NET team) implemented an HTTP check instead of a port check, but that's how it

Whoops, nevermind, really did misread the docs. Was as easy as: `cf cups mongo -p '{"address": "http://localhost:3526", "username": "foo", "password": "bar"}'`

Let's say I'm using an DBaaS provider or have setup a database in a non-cloudfoundry cluster, how do I add it as a user-provided service? Reading the documentation, and it isn't clear [to me at

Is there any way to limit request for specific app? For example: Limit concurrent request Limit request per second/munites/hours Limit bandwidth I think gorouter is the best location to do flow

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

I have enabled the plans to all orgs. And I logged into CF as a space developer in the same org as where the service broker is being registered. In the market place I am able to view both the plans,

You've said you can do this as an admin but not an OrgManager. Did you make the two service plans available to your org, or are they available to all orgs? If you did not do one of these things, only

I'm sharing my research on this as I was looking into this. I'm going to share my general understanding on Webhooks based on the original author who proposed the idea of webhooks. Webhooks --- Web

We will certainly be exploring what golang 1.6 means for http2 support in Gorouter. Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc. wrote:

Putting scoen(a)pivotal.io in the loop. wrote:

There is plan to support 1.6 for the GoRouter https://twitter.com/shalako/status/692570344595570688 No sure if this include http2. wrote:

Hi I'm also interesting this topic. Since Go1.6 will support h2 in std lib by default, is there any plans gorouter supports it ? -- Taichi Nakashima 2016年2月2日(火) 8:09 Daniel Mikusa

Your mileage may vary, but if you look at the full processes's environment there are differences. In our case, we'll see things like the ssh port in the diego environment but not the DEA, as well as