[
https://issues.apache.org/activemq/browse/CAMEL-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53544#action_53544
]
Hadrian Zbarcea edited comment on CAMEL-1886 at 8/8/09 10:50 AM:
-----------------------------------------------------------------
Claus, what about a Map<lowercase-header, <header, Object>> ?
The key would always be the lowercase header for searches and what not, but on
the wire and where it matters the original header value would be used.
I agree that having case sensitive headers doesn't make sense (i.e. having
'Foo' and 'foo' as different headers).
was (Author: hadrian):
Claus, what about a Map<lowercase-header, <header, Object>> ?
The key would always be the lowercase header for searches and what not, but on
the wire and where it matters the original header value would be used.
I agree that having cases sensitive headers doesn't make sense (i.e. having
'Foo' and 'foo' as different headers).
> Lookup headers from a Camel Message should be case agnostic
> -----------------------------------------------------------
>
> Key: CAMEL-1886
> URL: https://issues.apache.org/activemq/browse/CAMEL-1886
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
> Attachments: CAMEL_1886.patch, CaseInsensitiveMap.java
>
>
> Today the case matter so: getHeader("Foo") and getHeader("foo") is not the
> same.
> And for some protocols the header case do not matter such as
> - http
> - mail
> etc.
> And who would in real life want to send 2 headers that are different only
> depending on the case
> - Foo=me
> - foo=you
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
