fix: Content-Disposition header format to comply with RFC 2183 #11377
+79
−4
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.
Summary
Fixes
Closes #8914
Problem
The header was set as
filename="name.ext"which is invalid per RFC 2183.This caused parsing failures in third-party libraries.
Solution
Changed to
inline; filename="name.ext"format with proper disposition-type.Test
Added tests in
tests-unit/server_test/test_content_disposition.py