[jira] [Commented] (CXF-6244) ContentDisposition should support UTF-8 filenames

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309945#comment-14309945 ] 

Sergey Beryozkin commented on CXF-6244:
---------------------------------------

Hi Mark

IMHO it makes sense to check if the extension parameter ends with '*' and if yes then treat it per the RFC 5987 rules.
Please provide a patch
thanks

> ContentDisposition should support UTF-8 filenames
> -------------------------------------------------
>
>                 Key: CXF-6244
>                 URL: https://issues.apache.org/jira/browse/CXF-6244
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.0.0
>            Reporter: Mark Ford
>
> I have a need to support uploading files via a JAXRS web service interface with CXF. The file payload is modeled as an Attachment and everything works fine when the filenames are plain ASCII or ISO-8859-1. If the filename is passed as UTF-8 chars, then the name is mangled on the server.
> RFC 5987 describes an encoding scheme to support UTF-8 characters in HTTP Headers. It would be nice if the Attachment / Content-Disposition from CXF supported this. The workaround without this is to access the Content-Disposition header directly and parse the name yourself.
> Something along the lines of:
> Content-Disposition = "attachment; filename*=UTF-8''%c2%a3%20and%20%e2%82%ac%20rates
> Note that the filename param is actually named "filename*". Perhaps the ContentDisposition class should check for these variants first and fallback to the non-extended versions?
> If accepted as an issue, I could provide a test case and patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)