willem.jiang wrote:
>
> I did some refactoring on current DefaultHttpBinding[1], now you can
> override the populateMessageHeader in your HttpBinding.
>
> [1] https://issues.apache.org/activemq/browse/CAMEL-2673
>
Perhaps DefaultHttpBinding should be changed to leave
"application/x-www-form-urlencoded" POST bodies intact (of course it can
still propagate form params to the camel message headers). This would be
similar to the current querystring param behavior: these get propagated to
the camel message, but they don't get stripped from the "original"
querystring. Any downsides to this? The upside is less intrusive message
modifications which can be pretty destructive to proxying applications.
--
View this message in context:
http://old.nabble.com/jetty%3Ahttp-component-%22mangles%22-x-www-form-urlencoded-POST-in-message%3A-tp28348176p28367402.html
Sent from the Camel - Users mailing list archive at Nabble.com.
