Uses of Class
io.quarkus.vertx.http.runtime.security.ImmutablePathMatcher.ImmutablePathMatcherBuilder
Packages that use ImmutablePathMatcher.ImmutablePathMatcherBuilder
-
Uses of ImmutablePathMatcher.ImmutablePathMatcherBuilder in io.quarkus.vertx.http.runtime.security
Methods in io.quarkus.vertx.http.runtime.security that return ImmutablePathMatcher.ImmutablePathMatcherBuilderModifier and TypeMethodDescriptionTwo sorts of paths are accepted: - exact path matches (without wildcard); these are matched first and Quarkus does no magic, request path must exactly match - paths with one or more wildcard: - ending wildcard matches zero or more path segment - inner wildcard matches exactly one path segment few notes: - it's key to understand only segments are matched, for example '/one*' will not match request path '/ones' - path patterns '/one*' and '/one/*' are one and the same thing as we only match path segments and '/one*' in fact means 'either /one or /one/any-number-of-path-segments' - paths are matched on longer-prefix-wins basis - what we call 'prefix' is in fact path to the first wildcard - if there is a path after first wildcard like in the '/one/*\/three' pattern ('/three' is remainder) path pattern is considered longer than the '/one/*' pattern and wins for request path '/one/two/three' - more specific pattern wins and wildcard is always less specific than any other path segment character, therefore path '/one/two/three*' will win over '/one/*\/three*' for request path '/one/two/three/four'static <T> ImmutablePathMatcher.ImmutablePathMatcherBuilder<T>ImmutablePathMatcher.builder()ImmutablePathMatcher.ImmutablePathMatcherBuilder.handlerAccumulator(BiConsumer<T, T> handlerAccumulator)