Revert index.csr.html to default filename index.html

[albanx]

Command

new

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

index.html

Description

Reopening this issue as I have seen some interesting debates on closed as #29088

Who ever says that index.html defeats the purpose of SSR on the assumption that / is static by default or something like that is terrible wrong.

In a real world angular app there are pages that need SSR and others that do not need. Most of cases in Angular SSR is done with Lambda in AWS, using cloudfront functions, which are connected as well to the a S3 bucket. Now the S3 bucket can serve a static page or resource in case when SSR is not needed, and for the rest of the pages that need SSR request get redirect to lambda and are handled there.

With this breaking change, I notice today that all my static pages were not working when SSR was turned off, because normally CloudFront (but it is same for CDN providers) will just serve the content from an S3 bucket pointing at /, which in this case broke because the index.html did not exists anymore.

This change needs to be reverted. It is no sense that index.csr.html is renamed by angular CLI, if a developer needs to rename it, can very well do it manually in the deployment procedure.

Minimal Reproduction

Just create a minimal SSR angular app

Exception or Error

index.csr.html is procuded by default

Your Environment

19

Anything else relevant?

No response

[alan-agius4]

Thanks for opening the issue.

With SSR, the intent is for the server-rendered index.html to serve as the primary entry point. However, most CDNs and hosting providers default to serving static content unless explicitly configured to route requests through your SSR pipeline. If a static index.html is served directly, it bypasses the intended server-side rendering behavior.

Since this behavior has been consistent across several major versions, we don’t plan to revert this core aspect of the build output. Instead, our focus is on offering more flexible, explicit support for hybrid rendering scenarios.

Workaround for Your Current Setup

You can configure your CloudFront distribution’s Default Root Object to serve index.csr.html instead. Alternatively, you could use a cloud function to redirect requests for the root path to index.csr.html.

Hybrid Rendering API

For apps that combine SSR, CSR, and SSG, the new hybrid rendering APIs provide a cleaner, more native Angular solution. These APIs let you explicitly define rendering modes per route, minimizing the need for custom deployment workarounds.