camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] [Closed] (CAMEL-4693) http4 Component not exposing HttpContext
Date Thu, 21 Mar 2013 18:49:17 GMT

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

Christian Müller closed CAMEL-4693.
-----------------------------------

    Resolution: Fixed
    
> http4 Component not exposing HttpContext
> ----------------------------------------
>
>                 Key: CAMEL-4693
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4693
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jeff Segal
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0, 2.9.2
>
>         Attachments: http4-httpContext.patch
>
>
> HttpComponents 4.x provides a facility to use a HttpContext for a given request by calling
HttpClient.execute(HttpUriRequest, HttpContext), but it looks like the http4 Camel Component
doesn't have hooks to use this. Looking at the latest source of org.apache.camel.component.http4.HttpProducer,
I only see one way of calling HttpClient.execute():
>     protected HttpResponse executeMethod(HttpUriRequest httpRequest) throws IOException
{
>         return httpClient.execute(httpRequest);
>     }
> Perhaps this could be made available in a similar fashion to HttpClientConfigurer? (for
example creating a HttpContextConfigurer)
> My particular symptom is that I'm unable to force the http4 component to use preemptive
authentication, which relies on HttpContext in HttpClient 4.x. In HttpClient 3.x, this was
made possible by the HttpClientParams flag "authenticationPreemptive". However, it appears
that this was removed for 4.x in favor of using HttpContext because of security concerns.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message