Re: [vcap-dev] Re: Proposal for Context Path Routing
Stevo Slavić <sslavic at gmail.com...>
In this proposal and current Routes API docstoggle quoted message Show quoted text
<http://apidocs.cloudfoundry.org/217/routes/creating_a_route.html> I don't
see support for wildcards when defining context path based route. Am I
E.g. for resources like
I'd like all /foos/*/*/doSomeAction to be routed to one CF app, and all
/foos/*/*/doSomeOtherAction to be routed to a different CF app.
Did you consider supporting HTTP methods to be used for routing as well?
E.g. similar to previous example, I'd like some HTTP methods on particular
resources to be handled by separate app then the rest of the requests on
DELETE /foos -> route to one cf app
* /foos -> route to another cf app, where * means any HTTP method, most
specific rule wins strategy
Ideally one would be able to combine both wildcards in HTTP methods and in
path segments to define a routing rule.
Also I do not see context path routing support in CF CLI (v6.12.3) or a
ticket in CF CLI issues to add the support. Did I miss something there? If
not should I create new ticket?
On Tue, May 19, 2015 at 4:41 PM, sabith ks <sabithksme(a)gmail.com> wrote: