camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryadh Amar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1913) camel-jetty - Should support multipart/form posted data in the message body better
Date Thu, 10 Sep 2009 10:38:12 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54117#action_54117
] 

Ryadh Amar commented on CAMEL-1913:
-----------------------------------

While understanding that it should stay as it is, conforming to the spec, I still believe
it should be in the body, the next endpoint could be a file, with an implicit converter which
will pull the uploaded file from the request
in the case there are multiple attachments, the same implicit converter would be able to detect
this fact, and produce the files.

> camel-jetty - Should support multipart/form posted data in the message body better
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-1913
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1913
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-http, camel-jetty
>    Affects Versions: 2.0-M3
>            Reporter: Claus Ibsen
>             Fix For: 2.1.0
>
>
> See CAMEL-1801
> It does not work as expected as the posted data should be in the *body* and not as it
does currently stored as a message header with the body as a key and with an empty value!
> For instance sending a file using curl
> {code}
> curl -F data=@src/test/data/plain.txt http://localhost:9080/myapp/myservice
> {code}
> You want Camel to provide the file content in the body and the other as headers. But
what you get in the body is
> {code}
> ------------------------------30cc29f24df6
> Content-Disposition: form-data; name="data"; filename="plain.txt"
> Content-Type: text/plain
> Hello World
> This is the second line
> ------------------------------30cc29f24df6--
> {code}

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