Fix parsing zip64 extra field #209
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ZJONSSON it would be nice if you can merge this PR. |
|
@ZJONSSON we believe this would fix the FILE_ENDED issue we are seeing as well. Would it be possible to have it looked at? Thanks! |
|
@ZJONSSON - It would be awesome to have this PR merged. We've tested it extensively and running it in production. |
|
Any chance this can get merged soonish? please and ty |
|
@ZJONSSON any chance of merging this in? This would be quite helpful. Please |
nosferatu500
added a commit
to nosferatu500/unzipper
that referenced
this pull request
May 9, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
fields can be omitted in the zip64 extra field, see https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT, 4.5.3.
Thank you for great work!