[ https://issues.apache.org/activemq/browse/SM-795?page=comments#action_37791 ] Grégoire A. commented on SM-795: --------------------------------
Just 'Server' header are illegal from a HTTP Client, (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) and we have to remove it for the request. i can provide a patch for this. Date header are optional for client but the specification recommend this field for POST method with entity body. But we need to refresh, i don't know for the moment if jakarta HttpClient provides it (i think it does). we can remove it too. idem for Transfert-Encoding, i don't know it jakarta httpclient manages it. This field is for the entire Http message. > HTTP headers attached as properties may cause requests to fail > -------------------------------------------------------------- > > Key: SM-795 > URL: https://issues.apache.org/activemq/browse/SM-795 > Project: ServiceMix > Issue Type: Improvement > Affects Versions: 3.1 > Environment: W2KS, JDK1.5 > Reporter: Maxim Y. Tebenev > > When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP > headers as message properties. When forwarding the message to another > provider endpoint the properties goes as HTTP headers in request. For > example, the following request to the second provider endpoint will have > following headers: > POST /DeliveryService/DeliveryService HTTP/1.1 > Date: Wed, 27 Dec 2006 13:24:46 GMT > Server: Apache-Coyote/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml > Content-Length: 359 > SOAPAction: "" > User-Agent: Jakarta Commons-HttpClient/3.0 > Host: localhost:8082 > Server, Date and Transfer-Encoding headers are illegal in client request and > cause Apache Tomcat server to fail with 500 error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
