-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
"app/console router:match" doesn't properly work with several routes with identical paths but differens host restrictions #8811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The cause of the Bug - in Symfony/Component/Routing/Matcher/TraceableUrlMatcher :: matchCollection(). Instead of "return true" in
should be "continue"
|
There seems to be something wrong with your setup.
|
My apologies and thank you, Tobion! But it's just my mistake in this description because of rush. In real router config files we haven't these mistakes. I've corrected my description of issue, thank you, Tobion, one more time. |
…s (karolsojko) This PR was merged into the 2.3 branch. Discussion ---------- [Routing] Fix router matching pattern against multiple hosts | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #8811, #6744 | License | MIT | Doc PR | When you had a pattern that matched on multiple host then only the first one was displayed as "almost matching". Fixed router matching against the same pattern on multiple hosts so now it shows every "almost match" on different hosts. Commits ------- f727b22 [Routing] Fix router matching pattern against multiple hosts
If I have several routes with same path but different host restriction, the command "router:match" won't find any matches for urls, that really matches second (or next) routes.
For example, I have routes
and if I try to execute command
the command don't find any matches, if requested host not 'some.example.com'.
The text was updated successfully, but these errors were encountered: