Repository navigation
fix(fetch): prefer Max-Age over Expires in Set-Cookie - #43146
Conversation
Test results for "MCP"3 failed 9032 passed, 1495 skipped Merge workflow run. |
|
Hi, I'm the Playwright bot and I took a first look at the CI failures. 🟡 One failure is uncertain; two are confirmed pre-existing flakesThe cookie parsing change does not reach these MCP tests, so the failures look unrelated to this PR. However, I could not find the same DetailsThis PR only changes Uncertain
Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
68e0be8
into
microsoft:main
Summary
Max-Agenow takes precedence overExpiresinSet-Cookieregardless of attribute order, per RFC 6265 §5.3.Max-Agevalue that is not an integer (e.g.10abc) is now ignored, per RFC 6265 §5.2.2.Fixes #43077