Closed Bug 1689979 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 27421 - HTTP/1 status code tests

Categories

(Core :: DOM: Networking, task, P4)

Product:
Core
Component:
DOM: Networking
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
87 Branch
Tracking Flags:
Tracking Status
firefox87 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 27421 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/27421
Details from upstream follow.

b'Anne van Kesteren <annevk@annevk.nl>' wrote:

HTTP/1 status code tests

For https://github.com/whatwg/fetch/issues/1142.

The expectations match Safari, which seems to have the most reasonable behavior. In part this might be due Safari rejecting HTTP/0.9 entirely at this point?

This still allows for some behavior that HTTP does not, such as HTTP/1.1 9 OK, but that might be hard to get rid of? (I.e., require three digits always.)

cc @ddragana

Component: web-platform-tests → DOM: Networking
Product: Testing → Core

CI Results

Ran 15 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 16 subtests

Status Summary

Firefox

OK : 1
FAIL: 16

Chrome

OK : 1
FAIL: 16

Safari

OK : 1
FAIL: 16

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/fetch/h1-parsing/status-code.window.html
HTTP/1.1 (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 BLAH (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 0 OK : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 1 OK : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 99 NOT OK : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 077 77 : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 099 HELLO : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 200 : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 999 DOES IT MATTER : FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 1000 BOO (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 0200 BOO (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 65736 NOT 200 OR SOME SUCH (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 131072 HI (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 -200 TEST (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 0xA (network error): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP/1.1 C8 (network error): FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5eee1e354398 [wpt PR 27421] - HTTP/1 status code tests, a=testonly https://hg.mozilla.org/integration/autoland/rev/db350a650fb7 [wpt PR 27421] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/5eee1e354398
https://hg.mozilla.org/mozilla-central/rev/db350a650fb7

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox87: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in before you can comment on or make changes to this bug.