FILEUPLOAD-274: RFC 5987 compliance #24
Merged
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.
RFC 5987
adds support for encoding mechanism for use in MIME headers in HTTP headers. It recommends following formats<paramname>: <paramvalue>
<paramname>*: <charset>'<lang>'<percent-encoded>
The specification has following things to say
RFC 2231
- MIME Type extension for Email and other protocols to support multiple charsets and languages. (Having Asterisks (*
) at the end of parameter name for extensions)RFC 5987
- Extends onRFC 2231
for extended charsets and languages, but restricts charsets toUTF-8
andISO-8859-1
and no continuations (multiple extensions for same param name) as HTTP headers has no limitations in header sizeRFC 7578
- Extends onRFC 5987
specifically formultipart/form-data
, but rejects usage of Asterisks (*
)