Conditionally parse Zip64 extra field based on specification#596
Merged
adamhathcock merged 1 commit intoJun 4, 2021
Merged
Conversation
The Zip64 extra field should look for values based on the corresponding values in the local entry header. Fixes adamhathcock#595
|
@DannyBoyk thanks for solving this! It's incredible how many differences there can be in an outwardly standardised file format :D @adamhathcock any plans for merging this into an upcoming release? :) We would love to have this fix from the nuget package instead of changing our dependency. |
Owner
|
Thanks for this! |
1 task
This was referenced Apr 10, 2026
This was referenced May 9, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The Zip64 extra field should look for values based on the corresponding
values in the local entry header.
Fixes #595