A CXF-based proxy route creates multiple (two) user-agent HTTP headers, which
causes error responses from the recipient server.
In a proxy scenario, Camel is sending two user-agent HTTP headers from the
outbound endpoint.
The first is from the incoming client (SoapUI in this case). Interestingly
enough, the in-bound endpoint has lower-cased the header name (HTTP header
names are supposed to be case-insensitive; see RFC2616 section 4.2 "Message
Headers" [1]).
user-agent: Apache-HttpClient/4.1.1 (java 1.5)
User-Agent: Apache CXF 2.6.3
In this (and most? all?) scenarios, Camel/CXF should preserve the original
user-agent if it exists and not add a new one. I suspect the root cause may
be the handling of HTTP headers in a case-sensitive manner.
While multiple headers with the same name is allowed by RFC2616 4.2 [1]
under _certain conditions_, many HTTP server implementations allow it for
only certain headers, e.g., Set-Cookie. Otherwise, they return an error
response. In this particular case, Microsoft-IIS/7.5 Microsoft-HTTPAPI/2.0
returns a 400 response code and includes the following text in the response:
"HTTP Error 400. The request has an invalid header name."
A workaround is to remove incoming headers in the route by adding:
<removeHeader headerName="User-Agent" />
<removeHeader headerName="user-agent" />
or
<removeHeaders pattern="CamelHttp*" />
Although this has the minor undesirable effect of losing the original
user-agent information.
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html
Sent from the Camel - Users mailing list archive at Nabble.com.
