On Fri, Oct 19, 2012 at 10:50 AM, Oleg.Kasian <[email protected]> wrote: > It is actually in body, it is application/x-www-form-urlencoded. Seems like, > when jetty component receives such request, it parses request body to > exchange headers, passing them to endpoint. In this case, simple forwarding > like this: > > <from uri="jetty://http://0.0.0.0:7777/ws/predmine/controls"; /> > <to uri="http://10.1.193.197:8080/predmine/boards.xml?bridgeEndpoint=true"; > /> > > fails on large data. This doesn't work for requests sent directly from > browsers either. > Thanks to Raul, I was able to overcome the problem modifying my route: > > <from uri="jetty://http://0.0.0.0:7777/ws/predmine/controls"; /> > <removeHeaders pattern="*" /> > <setHeader headerName="content-type"> > <simple>application/x-www-form-urlencoded</simple> > </setHeader> > <to uri="http://10.1.193.197:8080/predmine/boards.xml?bridgeEndpoint=true"; > /> >
Ah seems like we should add some logic to support this use-case. As the application/x-www-form-urlencoded content-type should IMHO be parsed straight to the message body. Fell free to log a JIRA ticket. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Problems-when-forwarding-large-post-with-jetty-tp5721278p5721286.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
