Closed Bug 1696203 Opened 3 years ago Closed 2 days ago

If Content-Length exceeds actual length, stream should return a TypeError, not "AbortError" DOMException

Categories

(Core :: DOM: Networking, defect, P3)

Product:
Core
Component:
DOM: Networking
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: annevk, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

I wrote a test in https://github.com/web-platform-tests/wpt/pull/10548 fetch/content-length/too-long.window.js that checks what error a stream ends up with when Content-Length exceeds the actual length and we use the wrong exception.

ni myself to take a look.

Flags: needinfo?(kershaw)

Have no time to fix this for now, so put this in our backlog.

Severity: -- → S3
Flags: needinfo?(kershaw)
Priority: -- → P3
Whiteboard: [necko-triaged]

:kershaw, we pass this WPT now, so I suspect this has since been fixed. Shall we close this bug?

Status: NEW → RESOLVED
Closed: 2 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.