-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic transfer-decoding of file content for multipart-params #260
Labels
Comments
As a current workaround for guessing whether the data is still base64 encoded I use
|
In a related stack overflow post, there is a discussion as to whether this is a bug in the software (PHP in this case) or in the RFC: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When receiving a file via multipart-params, there is an (optional) key
"Content-Transfer-Encoding" with values 7bit (default), 8bit, binary and base64.
Depending on these values, the file or byte array (depending on the store used) should automatically be decoded to its original form.
Using Java7 or higher, one can use
(.decode (java.util.Base64/getDecoder) bytes)
to receive a new byte array with the real payload.This is an issue because upon receiving the data, the multpart-params middleware has the "Content-Transfer-Encoding" parameters available to select the correct decoding mechanism. But since the Content-Transfer-Encoding value is not transmitted further down the line, the actual consumer of the file has to guess the real Content-Transfer-Encoding.
The text was updated successfully, but these errors were encountered: