Closed Bug 1598298 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 20359 - Make DecompressionStream error checking stricter

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox72 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla72
Tracking Flags:
Tracking Status
firefox72 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Adam Rice <ricea@chromium.org> wrote:

Make DecompressionStream error checking stricter

Error the stream if the input to DecompressionStream is truncated, or
there is junk after the end of the stream. This will help avoid
accidental loss of data.

Also add a thorough test of the behaviour when various fields of a
compressed stream are corrupted. Also test that errors are correctly
issued when the stream is truncated or has trailing junk.

BUG=1014422

Change-Id: I8aceeafd279b75d4fea76d7edca19024856417c0
Reviewed-on: https://chromium-review.googlesource.com/1928428
WPT-Export-Revision: f4030ed5760bdaff7e0036b5180dc98f4b0b7ac1

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/61c3e8111428
[wpt PR 20359] - Make DecompressionStream error checking stricter, a=testonly
https://hg.mozilla.org/integration/autoland/rev/7b9a98686466
[wpt PR 20359] - Update wpt metadata, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/61c3e8111428
https://hg.mozilla.org/mozilla-central/rev/7b9a98686466

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