Angular 19 SSR nested redirectTo result in a redirect loop #28903

ManuelRauber · 2024-11-20T08:51:20Z

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:

export const routes: Routes = [
  {
    path: '',
    pathMatch: 'full',
    redirectTo: 'some',
  },
  {
    path: ':param',
    children: [
      {
        path: '',
        pathMatch: 'full',
        redirectTo: 'thing',
      },
      {
        path: 'thing',
        component: ExampleComponent,
      }
    ]
  }
];

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

`ERR_TOO_MANY_REDIRECTS` in the browser.

Please provide the environment you discovered this bug in (run `ng version`)

Angular CLI: 19.0.0
Node: 20.17.0
Package Manager: npm 10.8.2
OS: darwin arm64

Angular: 19.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.0
@angular-devkit/build-angular   19.0.0
@angular-devkit/core            19.0.0
@angular-devkit/schematics      19.0.0
@schematics/angular             19.0.0
rxjs                            7.8.1
typescript                      5.6.3
zone.js                         0.15.0

Anything else?

No response

The text was updated successfully, but these errors were encountered:

…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

…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes #28903

…router config This commit ensures proper handling of nested redirects that are implicitly structured but not explicitly defined in the router configuration. Closes #28903 (cherry picked from commit 34574b2)

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 transferred this issue from angular/angular Nov 20, 2024

alan-agius4 self-assigned this 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 mentioned this issue Nov 20, 2024

fix(@angular/ssr): handle nested redirects not explicitly defined in router config #28906

Merged

alan-agius4 closed this as completed in #28906 Nov 22, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Angular 19 SSR nested redirectTo result in a redirect loop #28903

Angular 19 SSR nested redirectTo result in a redirect loop #28903

ManuelRauber commented Nov 20, 2024 •

edited

Loading

Angular 19 SSR nested redirectTo result in a redirect loop #28903

Angular 19 SSR nested redirectTo result in a redirect loop #28903

Comments

ManuelRauber commented Nov 20, 2024 • edited Loading

Which @angular/* package(s) are the source of the bug?

Is this a regression?

Description

Please provide a link to a minimal reproduction of the bug

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Anything else?

ManuelRauber commented Nov 20, 2024 •

edited

Loading

Please provide the environment you discovered this bug in (run `ng version`)