CORB confirmation sniffing for HTML, XML and JSON security prefix. #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @annevk, @csreis, @GPHemsley,
This is my attempt to start documenting CORB confirmation sniffing algorithm (as tracked by #87 and in whatwg/fetch#681 (comment)).
I hope that this pull request is close to being acceptable, but I do note that:
and so it is likely that I made some newbie miskates. I am open to any feedback.
cover JSON sniffing (as implemented in Chromium in CrossOriginReadBlocking::SniffForJSON).
I hope that this omission is okay. I am worried that sniffing for JSON can end up more complicated
than the other kinds of sniffing, because 1) the current implementation requires a small state machine
and 2) the current implementation is imperfect (e.g. doesn't recognize JSON lists).
Please take a look?
-Lukasz
PS. I forgot to add my name to the contributors list. Let me fix this in a moment.
Preview | Diff