Re: Binding an App to the controller hostname


Jesse T. Alford
 

Tim,

Alternatively, if you don't want to have a separate system domain for
whatever reason, I recommend you create a "system" org and space with the
admin account and use create-route to reserve any routes you'd like to make
unavailable for use by apps on the shared domain. Having a separate system
domain is definitely cleaner, but if that doesn't work for you, this should
help.

On Tue, Feb 16, 2016 at 12:12 PM James Leavers <james(a)cloudhelix.io> wrote:

Hi,

Do you have separate system & app domains in your manifest? E.g.

properties:
domain: DOMAIN
system_domain: SYSTEM_DOMAIN
app_domains:
- APP_DOMAIN

If so you would be able to push an app to api.APP_DOMAIN, as the cf api is
on api.SYS_DOMAIN.

James


On 15 February 2016 at 17:15:00, Tim Lawrence (da_rude2k2(a)yahoo.co.uk)
wrote:

Hi all,

We have been testing one of our CF deployments and have found that we can
deploy an app bound to the "api" hostname. eg "api.domain.com".
It appears that the router then forwards traffic to this app rather than
the CF API. Clearly this is a fairly big problem for us.
This deployment is not currently completely up to date so wondered if
anyone else has seen this and if it has patched this in a subsequent
release?

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.