fix: Decode field names and filenames correctly #61
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
defnull
force-pushed
the
fix-60
branch
7 times, most recently
from
babed4d to
8ee7f0e
Compare
The WHATWG HTML5 specification defines that "field names and filenames for
file fields [...] must be escaped by replacing any 0x0A (LF) bytes with the
byte sequence %0A, 0x0D (CR) with %0D and 0x22 (") with %22. The user agent
must not perform any other escapes." and tests show that modern browsers
actually do that. This is different from traditional header quoting (which
involves backslash-escaping quotes and backslashes).
fixes #60
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.
See #60
Question 1: The new
content_disposition_[un]quote()functions have a really long name. Any better ideas? I wanted to distinguish those from the oldheader_[un]quote()functions.Question 2: We don't use the old quoting functions anymore, but others do. Keep them?Answer: Yes we use the old functions for all other headers (e.g. content-type). Do not deprecate them.