Closed
Bug 1579850
Opened 6 years ago
Closed 6 years ago
downloads API: Treat HTTP 204 (No Content) and HTTP 205 (Reset Content) as SERVER_BAD_CONTENT
Categories
(WebExtensions :: Compatibility, enhancement)
WebExtensions
Compatibility
Tracking
(firefox71 fixed)
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: nmaier, Assigned: nmaier)
References
Details
Attachments
(1 file)
Treating HTTP 204 (No Content) and HTTP 205 (Reset Content) as SERVER_BAD_CONTENT will create parity with Chrome.
It also is the right thing to do, as these status codes mark responses that do not actually contain any content that could reasonably be saved.
Thanks to Rob for pointing this out.
| Assignee | ||
Updated•6 years ago
|
Assignee: nobody → maierman
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by nbeleuzu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9336bba18082
Treat HTTP 204 and HTTP 205 as SERVER_BAD_CONTENT r=robwu
Keywords: checkin-needed
Comment 3•6 years ago
|
||
Thanks for the quick follow up and patch Nils!
Comment 4•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
| Assignee | ||
Updated•6 years ago
|
Flags: qe-verify-
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•