Fixed bug local block parsing data size, check for local size incomplete #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the ZIP Format Specification (version 6.3.10) it is defined that for a local file header (section 4.3.7) flag bit 3 (section 4.4.4) may be set to indicate that the data size can be found in the data descriptor. A supporting implementation must in that case set crc32, compressed and uncompressed size to zero.
From the specification:
We can therefore assume that if C/U size or crc32 is not set to zero in the local file header, the given size is valid and can be used to determine the content size
I observed that some zip compression utils in fact include the size in the local file header while still setting bit 3.
My contribution: