Repository navigation
docs(http,api): document origin-keyed agent clusters by default - #46305
Conversation
|
Sorry, since filing that issue I have retired, and am no longer available to provide review. |
|
No worries at all, thank you for letting me know! Wishing you the very best in your retirement. I'll leave this with the active MDN review rota. |
| ``` | ||
|
|
||
| By setting the `Origin-Agent-Cluster` header, a page can request that the browser allocate dedicated resources to this origin that are not shared with any other origins. | ||
| Under the current HTML specification, browsers place documents in origin-keyed agent clusters by default. This isolates same-site cross-origin documents from each other and prevents: |
There was a problem hiding this comment.
Words like "Under the current HTML specification" says nothing. MDN always documents the latest spec. What you need to do is add BCD for when that became the case in actual browsers
There was a problem hiding this comment.
Good point, thanks for catching that! Removed the time-relative spec phrasing across both documents so the behavior is stated directly. I'll also follow up with a PR in browser-compat-data for tracking when browsers enabled origin-keyed agent clusters by default.
|
Preview URLs (4 pages)
(comment last updated: 2026-10-31 01:29:11) |
Josh-Cena
left a comment
There was a problem hiding this comment.
Thank you. The remaining work is in mdn/browser-compat-data#30940
Closes #46194
Under WHATWG HTML PR whatwg/html#7617, agent clusters are specified to be origin-keyed by default.
This PR updates the documentation:
cc @domenic for review as offered in #46194.