summaryrefslogtreecommitdiff
path: root/test/fixtures/pseudo-multimember-gzip.gz
diff options
context:
space:
mode:
authorAnna Henningsen <sqrt@entless.org>2016-03-23 11:45:38 +0100
committerJeremiah Senkpiel <fishrock123@rocketmail.com>2016-03-23 13:04:19 -0400
commit0b3936b49f06743ea7aa48f4c03c99edf48afe80 (patch)
treeaddc57e06f2c4743c381a1151425773e98a63f37 /test/fixtures/pseudo-multimember-gzip.gz
parent7d73e60f60e2161457ca4c923008c9064a36bced (diff)
downloadnode-new-0b3936b49f06743ea7aa48f4c03c99edf48afe80.tar.gz
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.gz')
-rw-r--r--test/fixtures/pseudo-multimember-gzip.gzbin0 -> 161 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/test/fixtures/pseudo-multimember-gzip.gz b/test/fixtures/pseudo-multimember-gzip.gz
new file mode 100644
index 0000000000..a019c484d8
--- /dev/null
+++ b/test/fixtures/pseudo-multimember-gzip.gz
Binary files differ