summaryrefslogtreecommitdiff
path: root/src/url.c
diff options
context:
space:
mode:
authorTimo Teräs <timo.teras@iki.fi>2010-12-17 09:36:19 +0200
committerTimo Teräs <timo.teras@iki.fi>2010-12-17 09:47:24 +0200
commitf126316c791371bd3dfd7c348b10e93e49f5e2d4 (patch)
treeac297b61c112ce7426a271c24183af1907f9488a /src/url.c
parentcdeb9caaad10b15b56b41fd159d6fc73a6aac610 (diff)
downloadapk-tools-f126316c791371bd3dfd7c348b10e93e49f5e2d4.tar.gz
apk-tools-f126316c791371bd3dfd7c348b10e93e49f5e2d4.tar.bz2
apk-tools-f126316c791371bd3dfd7c348b10e93e49f5e2d4.tar.xz
apk-tools-f126316c791371bd3dfd7c348b10e93e49f5e2d4.zip
gunzip: fix ordering of boundary callbacks
The boundary callback should not happen until all the uncompressed data has been consumed. This previously seems to have worked because normally gzip library returns "no error" instead of the "stream end" if we extract exactly the amount of bytes remaining in the archive. (Perhaps this was changed in new zlib.) In any case, verification was broken with some apks due to this callback ordering issue.
Diffstat (limited to 'src/url.c')
0 files changed, 0 insertions, 0 deletions