Repository navigation
BUGFIX: Resource URIs rendered as "<host>_Resources/..." without slash - #73
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix broken resource URIs for documents rendered through NodeRenderingUriService.
buildControllerContextAndSetBaseUri() set only the routing base URI. FileSystemTarget then built resource URIs as _Resources/... (no slash between them) and cached that for the rest of the process, so every later document got the same broken host.
The fix sets the site's domain as the override on MultisiteFileSystemSymlinkTarget collections, or / when useRelativeResourceUris is on. It only does this when no override is set yet, so callers that set one explicitly keep it.