Skip to content

fix(http): prevent caching of responses with Set-Cookie headers - #69446

Closed
SkyZeroZx wants to merge 1 commit into
angular:20.3.xfrom
SkyZeroZx:backport/69385-to-20.3.x
Closed

fix(http): prevent caching of responses with Set-Cookie headers#69446
SkyZeroZx wants to merge 1 commit into
angular:20.3.xfrom
SkyZeroZx:backport/69385-to-20.3.x

Conversation

@SkyZeroZx

Copy link
Copy Markdown
Contributor

Backport of #69385 to 20.3.x.

Cherry-picks 80795de.

Skip HttpTransferCache serialization for HTTP responses that contain a
Set-Cookie header.

Cookie-setting responses commonly represent session-specific,
user-specific, or security-sensitive state. Serializing their bodies into
SSR TransferState can embed sensitive data into the generated HTML, where
it may be reused during hydration or replayed by a shared cache/CDN.

(cherry picked from commit 80795de)
@pullapprove
pullapprove Bot requested a review from thePunderWoman June 19, 2026 15:10
@angular-robot angular-robot Bot added the area: common/http Issues related to HTTP and HTTP Client label Jun 19, 2026
@ngbot ngbot Bot added this to the Backlog milestone Jun 19, 2026
@SkyZeroZx SkyZeroZx closed this Jun 19, 2026
@angular-automatic-lock-bot

Copy link
Copy Markdown

This pull request has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Jul 21, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area: common/http Issues related to HTTP and HTTP Client

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant