camel-jetty passes POST form data as exchange headers, which fails with large form data

Solution Verified - Updated -

Issue

Consider a Camel route that proxies HTTP requests from one camel-jetty endpoint to another. A client makes a POST request whose Content-Type is x-www-form-urlencoded. Although the request body consists of name/value pairs as would be found on a GET request, the data is carried in the message body, because this is a POST. Most webservers and HTTP clients have some kind of limit on how long a URI can be, but there is, or should be, no limit on a body.

On the face of it, a Camel route should be able to pass a message of this form with no difficulty. In practice, however, we run into problems related to HTTP header sizes. It isn't immediately obvious that there are any headers involved.

Environment

  • Red Hat JBoss Fuse
    • 6.1
    • 6.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.