cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-6832) Attachment content-disposition modification-date not parsed correctly
Date Wed, 16 Mar 2016 16:09:33 GMT

     [ https://issues.apache.org/jira/browse/CXF-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin updated CXF-6832:
----------------------------------
         Assignee: Sergey Beryozkin
    Fix Version/s: 3.0.9
                   3.1.6
                   3.2.0
      Component/s: Core

> Attachment content-disposition modification-date not parsed correctly
> ---------------------------------------------------------------------
>
>                 Key: CXF-6832
>                 URL: https://issues.apache.org/jira/browse/CXF-6832
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>            Reporter: Nicolas Daniels
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 3.2.0, 3.1.6, 3.0.9
>
>
> When deserializing multipart content as org.apache.cxf.jaxrs.ext.multipart.Attachment,
the org.apache.cxf.attachment.ContentDisposition data are not correctly filled in. Those valid
fields are not set:
>  * creation-date       date when content was created [RFC2183]
>  * modification-date   date when content was last modified [RFC2183]
>  * read-date           date when content was last read [RFC2183]
> Exemple of Rest WebService declaration:
> public void put(@PathParam("path") String path,
> 			@Multipart(value = "file", required = false) Attachment attachment) throws IOException
{
>     System.out.println(attachment.getContentDisposition().getParameter("modification-date"));
 --> always null
> }
> Actually, the REGEXP pattern used in ContentDisposition.CD_HEADER_PARAMS_PATTERN is not
correct as it doesn't include '-' character. So the key is not 'modification-date' but rather
'date' in the map.



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

Mime
View raw message