camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henryk Konsek (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-7506) [NettyHttp] Remove headerFilterStrategy option after resolving
Date Fri, 13 Jun 2014 06:31:05 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henryk Konsek resolved CAMEL-7506.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.14.0

Fixed in 0da7ade0b994a9404054aa0b3bb6eee02183994b .

> [NettyHttp] Remove headerFilterStrategy option after resolving
> --------------------------------------------------------------
>
>                 Key: CAMEL-7506
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7506
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.13.1
>            Reporter: Henryk Konsek
>            Assignee: Henryk Konsek
>             Fix For: 2.14.0
>
>
> In Camel Netty HTTP component, we don't remove {{headerFilterStrategy}} option from the
parameters, so it is propagated as a query parameter.
> When I create producer URL like this - {{netty-http:http://host.com?headerFilterStrategy=#headerFilterStrategy&foo=bar}}
I expect only {{foo=bar}} to be send as a query to to endpoint (while {{headerFilterStrategy=#headerFilterStrategy}}
should be resolved from the registry and removed from the parameters). This is how it works
in Jetty component for example.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message