-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Add resource header for mime sniffing #39167
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
Add resource header for mime sniffing #39167
Conversation
|
🔨 Triggering try run (#17494303264) for Linux (WPT) |
|
Test results for linux-wpt from try job (#17494303264): Flaky unexpected result (22)
Stable unexpected results that are known to be intermittent (35)
Stable unexpected results (30)
|
|
|
ad074e0 to
7de95e1
Compare
|
🔨 Triggering try run (#17495850559) for Linux (WPT) |
|
Test results for linux-wpt from try job (#17495850559): Flaky unexpected result (30)
Stable unexpected results that are known to be intermittent (34)
Stable unexpected results (6)
|
|
|
|
These crashes puzzle me. For some reason the parser aborts prior to loading the document. Maybe I should not perform load document if that's the case? But how could that have worked before... |
7de95e1 to
631b8af
Compare
|
The crashes I figured out by adding another guard to the aborted flag. I also had to rearrange a bunch of stuff regarding CSP/policy container, since the reordering of loading exposed that we were processing these in the wrong way. Added relevant spec functions to make that possible. |
|
🔨 Triggering try run (#17513512174) for Linux (WPT) |
|
Test results for linux-wpt from try job (#17513512174): Flaky unexpected result (31)
Stable unexpected results that are known to be intermittent (30)
Stable unexpected results (1)
|
|
|
631b8af to
9928a8b
Compare
The concept of a "resource header" is not well specced, since it is unclear what a "resource" is. That said, it most closely matches a "response" as part of the navigation params. With this change, we now delay loading the document until either two things happen: 1. We reached the end of the file 2. We processed 1445 bytes (as defined by spec) We initially store bytes in the resource header and then after loading parse the stored bytes. Any subsequent loading will process as before. Part of servo#14024 Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
9928a8b to
7ba10aa
Compare
|
I made the |
Seems like a flaky infrastructure failure |
The concept of a "resource header" is not well specced, since it is unclear what a "resource" is. That said, it most closely matches a "response" as part of the navigation params. With this change, we now delay loading the document until either two things happen: 1. We reached the end of the file 2. We processed 1445 bytes (as defined by spec) We initially store bytes in the resource header and then after loading parse the stored bytes. Any subsequent loading will process as before. Part of servo#14024 Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com> Signed-off-by: JasonHonKL <j2004nol@gmail.com>
The concept of a "resource header" is not well specced, since it is unclear what a "resource" is. That said, it most closely matches a "response" as part of the navigation params.
With this change, we now delay loading the document until either two things happen:
We initially store bytes in the resource header and then after loading parse the stored bytes. Any subsequent loading will process as before.
Part of #14024