Fix building of query string parameters in UrlHelper #1753
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomasherceg
approved these changes
Dec 15, 2023
exyi
force-pushed
the
fix-UrlHelper-query-string
branch
from
dae2573 to
5ee1620
Compare
exyi
force-pushed
the
fix-UrlHelper-query-string
branch
from
5ee1620 to
6cce4ac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
URL parameters were not properly URI-encoded when calling some overloads of
Context.RedirectToRouteorContext.RedirectToUrl.Versions affected: DotVVM 4.2.0, 4.2.1 and 4.2.2
Fixed in: DotVVM 4.2.3
Resolution: Update to DotVVM 4.2.3 or newer