This is an automated email from the ASF dual-hosted git repository. gfournier pushed a commit to branch camel-3.22.x in repository https://gitbox.apache.org/repos/asf/camel.git
commit 0277727773ef064982980424aa56b71c7d945ce2 Author: Gaelle Fournier <[email protected]> AuthorDate: Thu Mar 5 09:15:20 2026 +0100 CAMEL-23128: fix broken links --- .../camel-jetty/src/main/docs/jetty-component.adoc | 34 ++++++++++++++++++-- .../camel-spring/src/main/docs/spring-summary.adoc | 3 -- .../src/main/docs/undertow-component.adoc | 36 ++++++++++++++++++++-- 3 files changed, 65 insertions(+), 8 deletions(-) diff --git a/components/camel-jetty/src/main/docs/jetty-component.adoc b/components/camel-jetty/src/main/docs/jetty-component.adoc index 90ae00c0daeb..0182ada25359 100644 --- a/components/camel-jetty/src/main/docs/jetty-component.adoc +++ b/components/camel-jetty/src/main/docs/jetty-component.adoc @@ -102,8 +102,7 @@ the numerical IP address of this interface should be used as the host. If you need to expose a Jetty endpoint on all network interfaces, the `0.0.0.0` address should be used. -To listen across an entire URI prefix, see -xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty match wildcards]. +To listen across an entire URI prefix, see below. If you actually want to expose routes by HTTP and already have a Servlet, you should instead refer to the @@ -127,6 +126,37 @@ xref:languages:simple-language.adoc[Simple] (such as xref:languages:ognl-languag we could also test for the parameter value and do routing based on the header value as well. +== How do I let Jetty match wildcards? + +By default, Jetty will only match on exact uri's. But you can instruct Jetty to match prefixes. For example: + +[source,java] +---- +from("jetty://0.0.0.0:8123/foo").to("mock:foo"); +---- + +In the route above Jetty will only match if the uri is +an exact match, so it will match if you enter +`\http://0.0.0.0:8123/foo` but not match if you do +`\http://0.0.0.0:8123/foo/bar`. + +So if you want to enable wildcard matching you need to set `matchOnUriPrefix=true` as follows: + +[source,java] +---- +from("jetty://0.0.0.0:8123/foo?matchOnUriPrefix=true").to("mock:foo"); +---- + +So now Jetty matches any endpoints with starts with `foo`. + +To match *any* endpoint you can remove the prefix so it will match anything from the root: + +[source,java] +---- +from("jetty://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo"); +---- + + == Session Support The session support option, `sessionSupport`, can be used to enable a diff --git a/components/camel-spring/src/main/docs/spring-summary.adoc b/components/camel-spring/src/main/docs/spring-summary.adoc index 07b549e7128c..06a9bccd544a 100644 --- a/components/camel-spring/src/main/docs/spring-summary.adoc +++ b/components/camel-spring/src/main/docs/spring-summary.adoc @@ -396,9 +396,6 @@ the above example), then you can refer to the component using SpringCamelContext lazily fetching components from the spring context for the scheme name you use for Endpoint URIs. -For more detail see xref:manual:faq:how-do-i-configure-endpoints.adoc[Configuring -Endpoints and Components]. - == CamelContextAware If you want the `CamelContext` to be injected diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc b/components/camel-undertow/src/main/docs/undertow-component.adoc index db78238dbd31..83039550bc72 100644 --- a/components/camel-undertow/src/main/docs/undertow-component.adoc +++ b/components/camel-undertow/src/main/docs/undertow-component.adoc @@ -136,13 +136,43 @@ the numerical IP address of this interface should be used as the host. If you need to expose an Undertow endpoint on all network interfaces, the `0.0.0.0` address should be used. -To listen across an entire URI prefix, see -xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty match wildcards]. - If you actually want to expose routes by HTTP and already have a Servlet, you should instead refer to the xref:servlet-component.adoc[Servlet Transport]. + +== How do I let Jetty match wildcards? + +By default xref:components::jetty-component.adoc[Jetty] will only match on exact uri's. But +you can instruct Jetty to match prefixes. For example: + +[source,java] +---- +from("jetty://0.0.0.0:8123/foo").to("mock:foo"); +---- + +In the route above xref:components::jetty-component.adoc[Jetty] will only match if the uri is +an exact match, so it will match if you enter +`\http://0.0.0.0:8123/foo` but not match if you do +`\http://0.0.0.0:8123/foo/bar`. + +So if you want to enable wildcard matching you do as follows: + +[source,java] +---- +from("jetty://0.0.0.0:8123/foo?matchOnUriPrefix=true").to("mock:foo"); +---- + +So now Jetty matches any endpoints with starts with `foo`. + +To match *any* endpoint you can do: + +[source,java] +---- +from("jetty://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo"); +---- + + == Security provider To plugin security provider for endpoint authentication, implement SPI interface
