ContentDisposition should match attributes in a case-insensitive fashion #34383
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
spring-projects-issues
added
the
status: waiting-for-triage
Signed-off-by: Andras Dobrosi <dobrosi@gmail.com>
Signed-off-by: Andras Dobrosi <dobrosi@gmail.com>
bclozel
added
in: web
bclozel
changed the title
|
@dobrosi don't worry about the build failure, I'll take it from here. Thanks for your first contribution, I'll get back to you if I have any feedback. |
|
Thank you for your support. |
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.
File name is null bug. HTTP clients may send a file with a "FileName" attribute in the Content-Disposition header.
RFC 6266: 'The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename for storing the message payload.'
Signed-off-by: Andras Dobrosi dobrosi@gmail.com