/application1/a/b/c
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068p5745161.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
---
oute2:
http://0.0.0.0:8080/application1?matchOnUriPrefix=true"/>
...
request:
http://:8080/application1/a/b/c
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068p5745161.html
Sent from the Camel - Users mailing list archive at Nabble.com.
allow matching on wildcards, see
more details at
http://camel.apache.org/jetty
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068.html
> Sent from the Camel - Users mailing list archive a
s message in context:
> http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068p5745145.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter:
ny
of this?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068p5745145.html
Sent from the Camel - Users mailing list archive at Nabble.com.
> http://:8080/application1/a/b/c
>
> Because of the overlapping url but with the second route being
> more specific
> will this request go to the 2nd route, the 1st route, randomly
> to either or
> will something else occur?
>
>
>
> --
> View this mess
n context:
http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068.html
Sent from the Camel - Users mailing list archive at Nabble.com.
