Skip to content

fix(http): account for multiple cache control headers - #71381

Open
crisbeto wants to merge 1 commit into
angular:mainfrom
crisbeto:multiple-cache-control
Open

crisbeto wants to merge 1 commit into
angular:mainfrom
crisbeto:multiple-cache-control

Conversation

@crisbeto

Copy link
Copy Markdown
Member

Updates the logic that detects the Cache-Control header to account for multiple values. This is a bit of an edge case, but could technically happen.

Updates the logic that detects the `Cache-Control` header to account for multiple values. This is a bit of an edge case, but could technically happen.
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Oct 15, 2026
@angular-robot angular-robot Bot added the area: common/http Issues related to HTTP and HTTP Client label Oct 15, 2026
@ngbot ngbot Bot added this to the Backlog milestone Oct 15, 2026
@crisbeto
crisbeto requested a review from alan-agius4 October 15, 2026 14:58
@crisbeto
crisbeto marked this pull request as ready for review October 15, 2026 14:58
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: common/http Issues related to HTTP and HTTP Client target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants