-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Support more types of redirection during prerendering. Fixes #11591 #12418
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
Merged
SteveSandersonMS
merged 3 commits into
master
from
stevesa/11591-fix-redirection-during-prerendering
Jul 22, 2019
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
16 changes: 16 additions & 0 deletions
16
src/Components/test/testassets/BasicTestApp/PrerenderedRedirection.razor
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
@page "/prerendered-redirection" | ||
@inject IUriHelper UriHelper | ||
|
||
@{ | ||
throw new InvalidOperationException("The rendering logic should never be executed"); | ||
} | ||
|
||
@code { | ||
protected override Task OnInitializedAsync() | ||
{ | ||
var uri = UriHelper.GetAbsoluteUri(); | ||
var destination = uri.Substring(uri.IndexOf("?destination=") + 13); | ||
UriHelper.NavigateTo(destination); | ||
return Task.CompletedTask; | ||
} | ||
} |
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I'm digging around in this code, does it make sense to change the contract of this method (I can do it in my changes).
Basically it's surprising when something says you're going to get a URI, might be relative, might not be. Not handling one of those cases is the source of this bug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm open to either choice here.
Having the base class auto-resolve the URL does discard some info that might have been useful (e.g., maybe the implementer wants to vary behavior for relative vs absolute URLs for some reason), but after consideration, I can't think of any definite cases where it would really be disadvantageous.
However, if we're biasing decisions towards future back-compatibility concerns, then it would be safest to say that implementers are responsible for handling all the cases, since we can remove cases later but can't add new ones.
Overall, it won't matter much because the only people subclassing
UriHelperBase
are basically us, so I'm fine with whatever you choose.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with Steve, I was actually going to make that same comment in that PR until I saw that the implementations simply forward to the underlying location object in the browser.
It would be good to handle it as it would make the situation better for prerendering though.