camel-http converts headers to lower case

http://xxx.com/interfaces/ticket"; xxxsoapaction: sakarmi head User-Agent: Jakarta Commons-HttpClient/3.1 Host: iface.nrps.telekom.intra:8115 Content-Length: 1056 Content-Type: text/xml; charset=utf-8 http://old.nabble.com/camel-http-converts-headers-to-lower-case-tp28620717p28620717.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-http converts headers to lower case

Hi Which Camel version are you using? I just checked the camel trunk code, there is no code which turn the headers into lower case. Willem attilav wrote: Hi everyone, I'm trying to use the camel-http to send a soap request, however the camel exchange headers get converted to lowercase durin

AW: camel-http converts headers to lower case

: Dr. Bernhard Beck Geschäftsführer: Jochen Adenau, Hans-Günther Meier -Ursprüngliche Nachricht- Von: Willem Jiang [mailto:willem.ji...@gmail.com] Gesendet: Donnerstag, 20. Mai 2010 15:07 An: users@camel.apache.org Betreff: Re: camel-http converts headers to lower case Hi Which Camel

Re: camel-http converts headers to lower case

ket"; >> xxxsoapaction: sakarmi head >> User-Agent: Jakarta Commons-HttpClient/3.1 >> Host: iface.nrps.telekom.intra:8115 >> Content-Length: 1056 >> Content-Type: text/xml; charset=utf-8 >> >> > >> The remote side is case sensitive on http headers, and complies about an >> invalid soap action. >> >> Thanks >> attilav > > > -- View this message in context: http://old.nabble.com/camel-http-converts-headers-to-lower-case-tp28620717p28621053.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-http converts headers to lower case

ace.intra:8115/ticket";) >>> >>> what actually gets sent over the wire is: >>> >>> POST /fault_ticket HTTP/1.1 >>> myheader: akarmi head >>> soapaction: "http://xxx.com/interfaces/ticket"; >>> xxxsoapaction: sakarmi head >&

Re: camel-http converts headers to lower case

Oh, I found the key, it's a bug of camel-http. Current message header is using CaseInsensitiveMap[1] to store the header key and value. And the HttpProducer should use the map.entrySet() to access the value instead of use map.getKeySet() to go through the headers. I already create a JIRA[2]

Re: camel-http converts headers to lower case

t; .setHeader("myHeaDer", constant("akarmi head")) >>>>> .setHeader("xxxSOAPAction", constant("sakarmi head")) >>>>> .to("http://iface.intra:8115/ticket";) >>>>> >>>>> what actually gets sent over the wire is: >>>>> >>>>> POST /fault_ticket HTTP/1.1 >>>>> myheader: akarmi head >>>>> soapaction: "http://xxx.com/interfaces/ticket"; >>>>> xxxsoapaction: sakarmi head >>>>> User-Agent: Jakarta Commons-HttpClient/3.1 >>>>> Host: iface.nrps.telekom.intra:8115 >>>>> Content-Length: 1056 >>>>> Content-Type: text/xml; charset=utf-8 >>>>> >>>>> >>>> >>>>> The remote side is case sensitive on http headers, and complies about >>>>> an >>>>> invalid soap action. >>>>> >>>>> Thanks >>>>> attilav >>>> >>>> >>> >> > > > -- View this message in context: http://old.nabble.com/camel-http-converts-headers-to-lower-case-tp28620717p28621640.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-http converts headers to lower case

Hi attilav I'm afraid there is no workaround :( As we just cut the camel 2.3.0, I don't think this issue is a blocker issue of Camel, so I marked the JIRA to be resolve in camel 2.4.0. Maybe you can use the Fuse camel 2.3.0, which will come out in an month, if you can't wait for the Camel 2.4

Re: camel-http converts headers to lower case

Hi Use a custom HttpBinding as a work around On Thu, May 20, 2010 at 4:20 PM, Willem Jiang wrote: > Hi attilav > > I'm afraid there is no workaround :( > As we just cut the camel 2.3.0, I don't think this issue is a blocker issue > of Camel, so I marked the JIRA to be resolve in camel 2.4.0. >

Re: camel-http converts headers to lower case

As the fix is on the HttpProducer side, I'm afraid you need a customer HttpProducer to work around that issue. Willem Claus Ibsen wrote: Hi Use a custom HttpBinding as a work around On Thu, May 20, 2010 at 4:20 PM, Willem Jiang wrote: Hi attilav I'm afraid there is no workaround :( As w