cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-2533) Content disposition values don't have their quotes stripped
Date Fri, 13 Nov 2009 02:34:39 GMT

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

Benson Margulies updated CXF-2533:
----------------------------------

    Description: 
Given multipart/form-data.

Given a content-disposition of 

form-data; name="comment"

Accessing the attachment list from the injected context, and then getting a ContentDisposition
object for the attachment.


Calling ContentDisposition.getParameter("name") returns a string with the quotes still in
place!

This can't be intended, but changing it is incompatible and people might have written code
to work around the current behavior. I'm about to.


  was:
Given multipart/form-data.

Given a content-disposition of 

form-data; name="comment"

Calling ContentDisposition.getParameter("name") returns a string with the quotes still in
place!

This can't be intended, but changing it is incompatible and people might have written code
to work around the current behavior. I'm about to.



> Content disposition values don't have their quotes stripped
> -----------------------------------------------------------
>
>                 Key: CXF-2533
>                 URL: https://issues.apache.org/jira/browse/CXF-2533
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.2.4
>            Reporter: Benson Margulies
>
> Given multipart/form-data.
> Given a content-disposition of 
> form-data; name="comment"
> Accessing the attachment list from the injected context, and then getting a ContentDisposition
object for the attachment.
> Calling ContentDisposition.getParameter("name") returns a string with the quotes still
in place!
> This can't be intended, but changing it is incompatible and people might have written
code to work around the current behavior. I'm about to.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message