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.
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.