-
Couldn't load subscription status.
- Fork 373
Define opaque-response blocking (updated) #1755
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
base: main
Are you sure you want to change the base?
Conversation
|
From the build errors, it looks like mimesniff needs to export more terms, e.g. https://github.com/whatwg/mimesniff/blob/main/mimesniff.bs#L988 |
I'd like to reference them in whatwg/fetch#1755, hence this patch to export those two algorithms.
This is good enough for early review, but there are a number of issues that still need resolving: https://github.com/annevk/orb/labels/mvp. There are also some inline TODO comments. A PR against HTML is needed to ensure it passes the appropriate metadata for media element and classic script requests. We might also want to depend on HTML for parsing JavaScript.
…ent-range values` algorithm
fetch.bs
Outdated
| set of bytes, and ultimately falls back to a full parse due to unfortunate (lack of) design | ||
| decisions in the early days of the web platform. As a result there are still quite a few responses | ||
| whose secrets can end up being revealed to attackers. Web developers are strongly encouraged to use | ||
| the `<code http-header>Cross-Origin-Resource-Policy</code>` response header to defend them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The http-header attribute seems to cause a build error. Try dfn-type=http-header
This PR is based on what @annevk has proposed in #1442, with additional changes. It includes the
validate a partial responseand theContent-Range header parseralgorithm, plus the additional changes that Firefox has made in its implementation.#1442 had some discussions and references, and I wish I can keep them, but I don't have write access to annevk/orb, hence this PR. Please let me know if there's a better way to move this forward.
cc @zcorpan @annevk
TODO:
At least two implementers are interested (and none opposed):
Tests are written and can be reviewed and commented upon at:
Implementation bugs are filed:
The top of this comment includes a clear commit message to use.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff