Multipart filename support RFC6266 without language

[zapodot]

The RFC6266 does support having a language identifier as part of an encoded filename (content disposition param filename*), however the current Jersey Multipart parsing will not decode the filename if the language identifier is not present.

Example:

Content-Disposition: form-data; name=myfile; filename=myfile.pdf; filename*=utf-8''myfile.pdf

<content>

Currently when you bind this request to FormDataContentDisposition parameter the filename field value will be utf-8''myfile.pdf, but I would really expect it to be myfile.pdf

[jansupol]

This looks like it makes sense, we do not need to have the charset a part of the header, it is already in the String actual charset.