Will do a backport for this.

Thomas Termin (JIRA) wrote:
>      [ 
> https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Thomas Termin resolved SM-795.
> ------------------------------
> 
>        Resolution: Fixed
>     Fix Version/s: 3.2
> 
> Fixed! But it is configurable over HttpConfiguration(what means you can 
> change the behaviour via JMX as well as conf/component.properties) 
> 
> 
> Author: tterm
> Date: Fri Apr 27 06:00:19 2007
> New Revision: 533084
> 
> URL: http://svn.apache.org/viewvc?view=rev&rev=533084
> Log:
> SM-795 HTTP headers attached as properties may cause requests to fail
> 
> Modified:
>     
> incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java
>     
> incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java
>     
> incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java
>     
> incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java
> 
>> 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
>>         Assigned To: Thomas Termin
>>             Fix For: 3.2
>>
>>         Attachments: SM-795.patch
>>
>>
>> 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.
> 


-- 
Thomas Termin
_______________________________
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart

Tel    :  (+49) 0711 - 45 10 17 676
Fax    :  (+49) 0711 - 45 10 17 573
WWW    :  http://www.blue-elephant-systems.com
Email  :  [EMAIL PROTECTED]

blue elephant systems GmbH
Firmensitz      : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle

Reply via email to