-
Notifications
You must be signed in to change notification settings - Fork 25.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(http): exclude caching for authenticated HTTP requests #54746
Conversation
This update modifies the transfer cache logic to prevent caching of HTTP requests that require authorization. Closes: angular#54745
d1cd76d
to
dc72975
Compare
eb9d34b
to
1c12094
Compare
This PR was merged into the repository by commit 2258ac7. |
why this isn't marked as breaking change? |
Adding to above, for enterprise level applications, a lot of API's require header authentication as a basic way to protect the API. If the request is authenticated on the server side, why prevent it from being utilized on the client side? Personally, this has crushed our use of hydration and taken away all of the goodness until it is configurable. |
…ngular#54746)" This reverts commit 2258ac7. Closes: angular#55031
…ngular#54746)" This reverts commit 2258ac7. Closes: angular#55031
…ngular#54746)" This reverts commit 2258ac7. Closes: angular#55031
…ngular#54746)" (angular#55033) This reverts commit 2258ac7. Closes: angular#55031 PR Close angular#55033
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This update modifies the transfer cache logic to prevent caching of HTTP requests that require authorization.
Closes: #54745