You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeff Segal (Updated) (JIRA)" <ji...@apache.org> on 2012/04/06 20:05:22 UTC

[jira] [Updated] (CAMEL-4693) http4 Component not exposing HttpContext

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

Jeff Segal updated CAMEL-4693:
------------------------------

    Attachment: http4-httpContext.patch

Patch to add capability to specify a HttpContext in the http4 Component.
                
> 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
>         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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira