Title: SSR resolves relative `redirectTo` against the wrong base when the route path has several segments · Issue #34300 · angular/angular-cli · GitHub
Open Graph Title: SSR resolves relative `redirectTo` against the wrong base when the route path has several segments · Issue #34300 · angular/angular-cli
X Title: SSR resolves relative `redirectTo` against the wrong base when the route path has several segments · Issue #34300 · angular/angular-cli
Description: Command other Is this a regression? Yes, this behavior used to work in the previous version The previous version in which this bug was not present was No response Description When a request matches a route with a string redirectTo, @angu...
Open Graph Description: Command other Is this a regression? Yes, this behavior used to work in the previous version The previous version in which this bug was not present was No response Description When a request matches...
X Description: Command other Is this a regression? Yes, this behavior used to work in the previous version The previous version in which this bug was not present was No response Description When a request matches...
Opengraph URL: https://github.com/angular/angular-cli/issues/34300
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SSR resolves relative `redirectTo` against the wrong base when the route path has several segments","articleBody":"### Command\n\nother\n\n### Is this a regression?\n\n- [ ] Yes, this behavior used to work in the previous version\n\n### The previous version in which this bug was not present was\n\n_No response_\n\n### Description\n\nWhen a request matches a route with a string `redirectTo`, `@angular/ssr` answers with a 302 built from the route config, without running the router. If the route's own `path` has more than one segment, a **relative** `redirectTo` is resolved against the wrong base.\n\n`{ path: 'old/page', redirectTo: 'new/page' }`:\n\n- Server: `GET /old/page` returns `Location: /old/new/page` (a 404).\n- Router (in-app navigation to `/old/page`): `/new/page`.\n\nThe router replaces all segments matched by the redirecting route (`old/page`). The server only removes the last one (`page`). Routes whose path is a single segment or empty are not affected, which is probably why this has gone unnoticed.\n\n**Note: fixing this changes current behaviour.** `app_spec.ts` asserts the current result ([L207-L217](https://github.com/angular/angular-cli/blob/6ecbadaba2c3b3493b67d10b7757d8974bf9b8a1/packages/angular/ssr/test/app_spec.ts#L207-L217): `redirect/relative` → `/redirect/home`, the router gives `/home`), and an app could depend on it if it happens to have a route at the server-computed path.\n\n### Minimal Reproduction\n\n```sh\nnpx @angular/cli@22.2.2 new repro-app --ssr --defaults\ncd repro-app\n```\n\n`src/app/app.routes.ts`:\n\n```ts\nimport { Component } from '@angular/core';\nimport { Routes } from '@angular/router';\n\n@Component({ template: 'New page' })\nclass NewPage {}\n\nexport const routes: Routes = [\n { path: 'old/page', redirectTo: 'new/page' },\n { path: 'new/page', component: NewPage },\n];\n```\n\n`src/app/app.routes.server.ts` (server rendering, so the request reaches the redirect handling instead of a prerendered redirect page):\n\n```ts\nimport { RenderMode, ServerRoute } from '@angular/ssr';\n\nexport const serverRoutes: ServerRoute[] = [{ path: '**', renderMode: RenderMode.Server }];\n```\n\n```sh\nnpx ng build\nNG_ALLOWED_HOSTS=localhost PORT=4000 node dist/repro-app/server/server.mjs\ncurl -si 'localhost:4000/old/page' | grep -i '^location'\n```\n\nExpected: `location: /new/page` (where the router navigates). Actual: `location: /old/new/page`.\n\n### Exception or Error\n\n```text\n$ curl -si localhost:4000/old/page | head -3\nHTTP/1.1 302 Found\nX-Powered-By: Express\nlocation: /old/new/page\n```\n\n### Your Environment\n\n```text\n _ _ ____ _ ___\n / \\ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|\n / △ \\ | '_ \\ / _` | | | | |/ _` | '__| | | | | | |\n / ___ \\| | | | (_| | |_| | | (_| | | | |___| |___ | |\n /_/ \\_\\_| |_|\\__, |\\__,_|_|\\__,_|_| \\____|_____|___|\n |___/\n\n\nAngular CLI : 22.2.2\nAngular : 22.2.2\nNode.js : 24.18.0\nPackage Manager : npm 11.16.0\nOperating System : linux x64\n\n┌───────────────────────────┬───────────────────┬───────────────────┐\n│ Package │ Installed Version │ Requested Version │\n├───────────────────────────┼───────────────────┼───────────────────┤\n│ @angular/build │ 22.2.2 │ ^22.2.2 │\n│ @angular/cli │ 22.2.2 │ ^22.2.2 │\n│ @angular/common │ 22.2.2 │ ^22.2.0 │\n│ @angular/compiler │ 22.2.2 │ ^22.2.0 │\n│ @angular/compiler-cli │ 22.2.2 │ ^22.2.0 │\n│ @angular/core │ 22.2.2 │ ^22.2.0 │\n│ @angular/forms │ 22.2.2 │ ^22.2.0 │\n│ @angular/platform-browser │ 22.2.2 │ ^22.2.0 │\n│ @angular/platform-server │ 22.2.2 │ ^22.2.0 │\n│ @angular/router │ 22.2.2 │ ^22.2.0 │\n│ @angular/ssr │ 22.2.2 │ ^22.2.2 │\n│ rxjs │ 7.8.2 │ ~7.8.0 │\n│ typescript │ 6.0.3 │ ~6.0.2 │\n└───────────────────────────┴───────────────────┴───────────────────┘\n```\n\n### Anything else relevant?\n\n[`resolveRedirectTo` in `ng-routes.ts#L543-L554`](https://github.com/angular/angular-cli/blob/6ecbadaba2c3b3493b67d10b7757d8974bf9b8a1/packages/angular/ssr/src/routes/ng-routes.ts#L543-L554) removes one segment (`segments.pop()`), while the router's `applyRedirectCommands` replaces all segments consumed by the route.\n\nRelated: #33504 / #33516 (parameters in the same function).\n\nI have a fix with tests and will open a PR for it. It updates the two `app_spec` expectations above to the router's result. If the current behaviour is intended, or this should wait for a major, I'm happy to adjust.\n\nNot browser specific. Seen with the default Express `server.ts` generated by `ng new --ssr`; the redirect comes from `AngularNodeAppEngine.handle()`, not from Express itself.\n","author":{"url":"https://github.com/bschaeublin","@type":"Person","name":"bschaeublin"},"datePublished":"2026-10-09T21:32:18Z","url":"https://github.com/angular/angular-cli/issues/34300"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:cae3a772-5b3d-7c7f-4319-39a76cca6955 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A95E:A3D97:17CE5D:2148F7:6AFDDA2D |
| html-safe-nonce | 8bedaeedd6426d16da41675eacfcfe482f60c504c8c995870eb54239c290604d |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBOTVFOkEzRDk3OjE3Q0U1RDoyMTQ4Rjc6NkFGRERBMkQiLCJ2aXNpdG9yX2lkIjoiMzE0Njc0OTYwMjcxNjA0NzkxNyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 25bf509aca0240ff62506cc82ad11aed4742b97269e7a18f239e21abd4b61937 |
| hovercard-subject-tag | issue:5784914059 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular-cli/34300/issue_layout |
| twitter:image | https://opengraph.githubassets.com/97db415dd56ad03fe94f10bfd44de1765cc0cc7aa54dfb93b96bf00ae6b889fd/angular/angular-cli/issues/34300 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/97db415dd56ad03fe94f10bfd44de1765cc0cc7aa54dfb93b96bf00ae6b889fd/angular/angular-cli/issues/34300 |
| og:image:alt | Command other Is this a regression? Yes, this behavior used to work in the previous version The previous version in which this bug was not present was No response Description When a request matches... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | bschaeublin |
| hostname | github.com |
| expected-hostname | github.com |
| None | 9918bd4004419458bcd838065ac2a76b76ebd11705d73909fff5ab99e996fa23 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular-cli git https://github.com/angular/angular-cli.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 36891867 |
| octolytics-dimension-repository_nwo | angular/angular-cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 36891867 |
| octolytics-dimension-repository_network_root_nwo | angular/angular-cli |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | a231c174493a6a442c0b0544475c918b30128208 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width