diff options
| author | Anna Henningsen <sqrt@entless.org> | 2016-03-23 11:45:38 +0100 |
|---|---|---|
| committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2016-03-23 13:04:19 -0400 |
| commit | 0b3936b49f06743ea7aa48f4c03c99edf48afe80 (patch) | |
| tree | addc57e06f2c4743c381a1151425773e98a63f37 /test/fixtures/pseudo-multimember-gzip.z | |
| parent | 7d73e60f60e2161457ca4c923008c9064a36bced (diff) | |
| download | android-node-v8-0b3936b49f06743ea7aa48f4c03c99edf48afe80.tar.gz android-node-v8-0b3936b49f06743ea7aa48f4c03c99edf48afe80.tar.bz2 android-node-v8-0b3936b49f06743ea7aa48f4c03c99edf48afe80.zip | |
zlib: Fix handling of gzip magic bytes mid-file
Only treat the gzip magic bytes, when encountered within the file
after reading a single block, as the start of a new member when
the previous member has ended.
Add test files that reliably reproduce #5852. The gzipped file
in test/fixtures/pseudo-multimember-gzip.gz contains the gzip
magic bytes exactly at the position that node encounters after having
read a single block, leading it to believe that a new data
member is starting.
Fixes: https://github.com/nodejs/node/issues/5852
PR-URL: https://github.com/nodejs/node/pull/5863
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'test/fixtures/pseudo-multimember-gzip.z')
| -rw-r--r-- | test/fixtures/pseudo-multimember-gzip.z | bin | 0 -> 148 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/test/fixtures/pseudo-multimember-gzip.z b/test/fixtures/pseudo-multimember-gzip.z Binary files differnew file mode 100644 index 0000000000..e87b13ab53 --- /dev/null +++ b/test/fixtures/pseudo-multimember-gzip.z |