fix: content-disposition filename regexp #87
Merged
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
Touffy
reviewed
Nov 12, 2024
…th white space + non latin filename in utf8
Touffy
pushed a commit
that referenced
this pull request
Nov 13, 2024
* Fix: Improve Content-Disposition filename matcher - handle white space + extended filename* in UTF-8 --------- Co-authored-by: maxime.abehserra <[email protected]>
Touffy
added a commit
that referenced
this pull request
Nov 13, 2024
* Fix: Improve Content-Disposition filename matcher - handle white space + extended filename* in UTF-8 --------- Co-authored-by: maxime.abehserra <[email protected]>
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.
Related issue: #86 (comment)
When filename is not in the last position, some files ended with
";at the end of its name when included in the zip archive.