Hi We might need to expose somekind of easier injection / alternation of the xxxHeaderFilterStrategyt the endpoint is configued with. So end users as in this case easily can customize it. In some cases end-users doesn't want to filter all headers, and in others they do.
It should be easily configurable from spring XML as well. Qucikly looking at the http component you need to alter the HttpComponent to set your own HttpHeaderFilterStrategy. I think it should be configurable on the endpoint, then end users can set a URI option, or a setter on the endpoint itself. Then it's easily configurable in Spring as well. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: 17. september 2008 01:46 To: [email protected] Subject: Re: Proxying web services Hi Micheal, The CAMEL-766[1] will explain this stripping for handling the "ProtocolHeaders". You can override the HttpHeaderFilterStrategy yourself and inject it into the http component. [1] https://issues.apache.org/activemq/browse/CAMEL-766 Willem Michael.Murphree wrote: > One more item on this. In camel-http (1.4.0 and 1.5.0), the HttpBinding > class deliberately filters out the Content-Type header on the HttpResponse > object. This causes a web service response to fail. Why does the binding > strip out the "Content-Type" header from the response? > > Is there a way to add it back in short of touching that code? > > Regards, > > Michael >
