1. posterid:472663
  2. Wildcard routes, subdomains and failing smoke-test

Re: Wildcard routes, subdomains and failing smoke-test

Dieu Cao <dcao@...>
 

You might consider making a tiny custom 404 app and then map *.cf.bar.io
and *.foo.bar.io and any other sub domains to it so that it doesn't fall
through to your landing page app.
Would that work for you?

-Dieu
CF CAPI PM

On Wed, Feb 3, 2016 at 12:46 AM, Engelke, Johannes <info(a)johannes-engelke.de
wrote:
Hi,
we got the following problem and I would like to know, if you have an idea
how to solve it.

We setup a view domains:
- bar.io
- foo.bar.io
- cf.bar.io

Bar.io <http://bar.io> is used for all the end user related things like
the landing page, documentation, etc. foo.bar.io is used for internal
service endpoints and cf.bar.io is used for all stuff related to CF (api,
uaa, login…) and some shared things like monitoring UI etc.

I created a route *.bar.io to move all typos etc. of our customer touch
points to the central landing page. I was expecting <random>.cf.bar.io
will be still return an 404 Route not found. Now smoketests (using
cf.bar.io) are failing, because the wildcard domain is working recursive
for all subdomains and is returning the content of *.bar app. (See:
https://github.com/cloudfoundry/cf-smoke-tests/blob/master/smoke/runtime/runtime_test.go#L87-L93
)

*.bar.io -> landing-page-app
*.cf.bar.io -> landing-page-app (why?)
*.foo.bar.io -> landing-page-app (why?)

So my question, were should we fix it? Should the gorouter not be
recursive over subdomains? Should we change the smoketest? Or am I on the
wrong track and we should do something else?

Cheers
Johannes

?
attachment.html

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