Validate response status and MIME type in WorkerGlobalScope::ImportScripts#40023
Conversation
WorkerGlobalScope::ImportScripts
3b6558e to
54b02cc
Compare
|
🔨 Triggering try run (#18652601184) for Linux (WPT) |
|
Test results for linux-wpt from try job (#18652601184): Flaky unexpected result (19)
Stable unexpected results that are known to be intermittent (24)
Stable unexpected results (3)
|
|
|
|
Can you update the expected test results to account for the new passing tests? https://book.servo.org/hacking/testing.html#updating-web-platform-test-expectations |
Okay, I'll do it. |
|
There is a fail now: the same test case pass when using a data url |
This test remains failing. I investigated and found the cause: For blob: URLs with malformed MIME parameters (e.g., buf.type_string.parse().unwrap_or(mime::TEXT_PLAIN)This causes the Content-Type header to be set to In contrast, data: URLs work correctly because the Should we:
See try build results. |
|
That being said, I think doing that switch in a separate PR would make sense. |
…cripts` Signed-off-by: WaterWhisperer <[email protected]>
Signed-off-by: WaterWhisperer <[email protected]>
2030319 to
cc29526
Compare
|
Thanks for the guidance! I've updated the WPT expectations to mark the blob: URL test with malformed MIME parameters ( As you mentioned, switching to |
Changes
NetworkErroron failure, as required by the specFixes: #39993