…ver and client

Expose HTTP_TRANSFER_CACHE_ORIGIN_MAP in public api. This token can be used when different origins are used to access the same APIs between server and browser.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Feature

What is the current behavior?

Angular SSR applications are sometimes deployed in an internal private network where APIs must be accessed with a different origin that the external urls used from the client application.

Currently, such requests cannot be reused in the client during hydration because the urls do not match in the transfer state.

Issue Number: #53702

What is the new behavior?

Such applications can provide an origin map between server and clients by providing HTTP_TRANSFER_CACHE_ORIGIN_MAP.

The requests made on the client to the external origin will be correctly reused.

// in app.server.config.ts
{
    provide: HTTP_TRANSFER_CACHE_ORIGIN_MAP,
    useValue: {
        'http://internal-domain:80': 'https://external-domain:443'
    }
}

// Alternative usage with dynamic values (depending on stage or prod environments)
{
    provide: HTTP_TRANSFER_CACHE_ORIGIN_MAP,
    useFactory: () => {
        const config = inject(ConfigService);
        return {
            [config.internalOrigin]: [config.externalOrigin],
        };
    }
}

The origin map must be provided only in the server application.
A Runtime error will be thrown when the token is present in the client-side application.

Does this PR introduce a breaking change?

• Yes
• No

Other information