cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-6244) ContentDisposition should support UTF-8 filenames
Date Sat, 07 Feb 2015 04:18:34 GMT

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

ASF GitHub Bot commented on CXF-6244:
-------------------------------------

GitHub user massfords opened a pull request:

    https://github.com/apache/cxf/pull/52

    CXF-6244

    - add support for Content-Disposition's filename* which allows for UTF-8 encoded values

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/massfords/cxf master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/52.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #52
    
----
commit 897b20ba8ab4e4926f97e200336f71d9af9f2898
Author: Mark Ford <mark@massfords.com>
Date:   2015-02-07T04:10:52Z

    CXF-6244
    - add support for Content-Disposition's filename* which allows for UTF-8 encoded values

----


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

Mime
View raw message