-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Incorrect route matching logs in web profiler for route with condition and query parameters #25206
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 fix you are referring to removes the request attributes from the request trace and actually breaks the correct behaviour. It causes the web profiler to output the incorrect route matching logs because the trace lacks the route query attributes. I understand that some request attributes (like mentioned closure) could cause problems but the query should be safe to store. |
Hey, thanks for your report! |
Friendly reminder that this issue exists. If I don't hear anything I'll close this. |
Status: Reviewed |
see #39708 |
… account when matching routes (xabbuh) This PR was merged into the 4.4 branch. Discussion ---------- [WebProfilerBundle] take query and request parameters into account when matching routes | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #25206 | License | MIT | Doc PR | Commits ------- 28b6051 take query and request parameters into account when matching routes
The web profiler's route matching logs do not seem to correctly match the route although the route is in fact matched. Given we have a route configuration:
The URL
project.dev/app_dev.php/magazin?page=123
will be correctly mapped to that route but the profiler information does not seem to properly report that in the logs:I think this is related to #20621 and probably can be fixed in https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/WebProfilerBundle/Controller/RouterController.php#L86:
The text was updated successfully, but these errors were encountered: