fix(router): fall back when serializing protocol-relative URLs - #71094
Merged
Merged
Conversation
alan-agius4
reviewed
Sep 30, 2026
atscott
force-pushed
the
fix/router-relative-url
branch
2 times, most recently
from
September 30, 2026 16:18
aa3c990 to
e8098db
Compare
Avoid throwing when DefaultUrlSerializer encounters a UrlTree that would serialize to a protocol-relative URL. Warn in development mode and serialize the tree with a root-relative path instead while preserving query parameters and fragments. Additionally, account for WHATWG URL normalization (e.g. dot segments and backslashes collapsing into protocol-relative paths such as `/.//` or `/..//`). Fixes angular#69700 Fixes angular#71076 Co-authored-by: Andrew Scott <atscott01@gmail.com>
atscott
force-pushed
the
fix/router-relative-url
branch
from
September 30, 2026 17:14
e8098db to
f10507e
Compare
atscott
added
action: merge
kirjs
approved these changes
Oct 2, 2026
Contributor
This was referenced Oct 2, 2026
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
4 participants
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.
Avoid throwing when DefaultUrlSerializer encounters a UrlTree that would serialize to a protocol-relative URL. Warn in development mode and serialize the tree with a root-relative path instead while preserving query parameters and fragments.
Additionally, account for WHATWG URL normalization (e.g. dot segments and backslashes collapsing into protocol-relative paths such as
/.//or/..//).Fixes #69700
Fixes #71076