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

common

Is this a regression?

Yes

Description

Previously, we were able to use hydration/http caching with all of our requests from the server to the client. With 17.3.0 (#54746) caching was killed for all requests with authorization headers, but with enterprise applications, this is almost always the case. Therefore, hydration does not occur properly and the application behaves poorly.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

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

17.3.0

Anything else?

A solution would be to revert this behavior, or to add a configurable bit to the withHttpTransferCacheOptions config. As is, this prevents myself and likely others from upgrading past 17.2