-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Problem passing query parameters to redirected Url #26256
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 |
@Tobion Yes, that's what I guessed too. |
@cooldude77 do you want to provide a PR for this feature ? |
@Simperfit I am yet to understand the PR process completely ( because I recently found one more feature which was added and it was the first time I did something like this). So it would be great if anyone else ( or yourself ) can pick it up. Best regards |
I'm going to do it ;). |
This PR was merged into the 4.1-dev branch. Discussion ---------- [FrameworkBundle] keep query in redirect | Q | A | ------------- | --- | Branch? | 4.1 | Bug fix? | no | New feature? | yes <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | no <!-- don't forget to update UPGRADE-*.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #26256 <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | #9314 <!-- Write a short README entry for your feature/bugfix here (replace this comment block.) This will help people understand your PR and can be used as a start of the Doc PR. Additionally: - Bug fixes must be submitted against the lowest branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch. --> Commits ------- 406bfc9 [FrameworkBundle] keep query params in redirection
Uh oh!
There was an error while loading. Please reload this page.
Here is one of my route
And this redirects to
So a sample URI for testing would be
'api/v2/connections/self/with/users/status/connectedSince/pages/1'
But there could be more get params supplied by client, which may not form part of url in routing( look at the params after ? mark)
'api/v2/connections/self/with/users/status/connectedSince/pages/1?device=android&density=XXHDPI&xy=blah',
Since the routes have same number of parameter
{page}
gets passed correctly but thedevice
anddensity
are not passed to the 'routed to' controller.The problem could be that RedirectController does not look for the request parameter at line 65.
Adding to route params also does not help as density value for example is not copied
And since target controller does not receive right request, it does not get the params leading to
Either device or density information is missing (404 Not Found)
The text was updated successfully, but these errors were encountered: