Expand description
Defines the type RouteMatcher and default implementations.
Structs
- A
RouteMatcherthat succeeds when theRequesthas been made with anAcceptheader that includes one or more supported media types. A missingAcceptheader, or the value of*/*will also positvely match. It supports the quality weighted syntax, but does not take the quality into consideration when matching. - A route matcher that checks whether the value of the
Access-Control-Request-Methodheader matches the defined value. - Allows multiple
RouteMatchervalues to be combined when accessing a request. - Matches any request without restriction (i.e. will accept any request which has already matched the path to the current route). For example, this matcher is used when delegating a path prefix to another router.
- A
RouteMatcherthat succeeds when theRequesthas been made with aContent-Typeheader that includes a supported media type. The matcher will fail if the Content-Type header is missing, unless you callallow_no_typeon it. - A
RouteMatcherthat succeeds when theRequesthas been made with an accepted HTTP request method.
Traits
- Allow various types to represent themselves as a
RouteMatcher - Determines if conditions required for the associated
Routeto be invoked by theRouterhave been met.