-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Angular 19 SSR nested redirectTo result in a redirect loop #28903
Labels
area: @angular/ssr
freq1: low
Only reported by a handful of users who observe it rarely
severity3: broken
type: bug/fix
Comments
ManuelRauber
changed the title
Angular 19 SSR multiple redirectTo result in a redirect loop
Angular 19 SSR nested redirectTo result in a redirect loop
Nov 20, 2024
alan-agius4
added
type: bug/fix
freq1: low
Only reported by a handful of users who observe it rarely
severity3: broken
area: @angular/ssr
labels
Nov 20, 2024
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 20, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 20, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 20, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 20, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 20, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 21, 2024
…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes angular#28903
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: @angular/ssr
freq1: low
Only reported by a handful of users who observe it rarely
severity3: broken
type: bug/fix
Which @angular/* package(s) are the source of the bug?
router
Is this a regression?
Yes
Description
Using the following routes in Angular 19 with SSR enables leads to an
ERR_TOO_MANY_REDIRECTS
error:The behavior in Angular 18 SSR: If you go to
/
you're redirected to/some
which redirects to/some/thing
.The behavior in Angular 19 SSR: If you go to
/
you get stuck in a redirect loop which tries to redirect to/thing
. So, it looks like the nested redirect is not adding the parent route but tries redirect to a root route.The same routing works in Angular 19 without SSR.
Please see the linked example and read the README there for setting up the example.
Please provide a link to a minimal reproduction of the bug
https://github.com/ManuelRauber/angular-19-ssr-redirect-issue
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: