Expected route selection prioritization with RegularExpression #4849
Unanswered
BadLiveware
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Route selection priority
It seems like its not possible to override routing selection via more specific matches using regex and query parameters,
I would expect that if two
RegularExpression
paths matches, other match attributes would be used as tie breakers, for example queryParams.This is a simplified example:
Default everything to the backend
old-web
viaPathPrefix: /
Override other HTTPRoutes to
old-web
on regex.*
AND query parameternext=0
Match a specific route(
(/<i18n>)?/valuation
) tonextweb
Try to override that route by going to
/en/valuation?next=0
, the selected route will benextweb
Try to override that route by going to
/en/valuation?ow=1
, the selected route will benextweb
What is the expected outcome of the route selection in this situation?
Beta Was this translation helpful? Give feedback.
All reactions