Re: Adding second domain to API endpoint
James, would'nt a second domain (even if resolving to the same IP than the
toggle quoted messageShow quoted text
primary domain, thanks to a CNAME), still be mentionned in http requests in their original "Host:", header and would therefore be unknown to the CF gorouter, returning a 404 as a response ? I wonder whether the routing-api [1] indeed currently returns a wildcard route to the CC IP/port, and could then be used to advertise a new wildcard route in a second domain. This would require custom development into a distinct bosh jobs (that would periodically renew the new domain before its TTL expires) Guillaume. [1] https://github.com/cloudfoundry-incubator/routing-api#usage
On Sat, Jun 6, 2015 at 6:38 PM, James Bayer <jbayer(a)pivotal.io> wrote:
it appears as though the cloud controller only supports advertising a
|
|