Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 1 Mar 2014 06:57:21 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12698093.1393649002370.129791.1393657041451@arcas>
In-Reply-To: <JIRA.12698093.1393649002370@arcas>
References: <JIRA.12698093.1393649002370@arcas>
Subject: [jira] [Updated] (CAMEL-7260) Documentation Bug - HTTP4 Component
 Configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-7260:
-------------------------------

    Priority: Trivial  (was: Minor)

> Documentation Bug - HTTP4 Component Configuration
> -------------------------------------------------
>
>                 Key: CAMEL-7260
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7260
>             Project: Camel
>          Issue Type: Task
>          Components: camel-http4, documentation
>            Reporter: Stephen Swensen
>            Priority: Trivial
>
> There is a bug in the HTTP4 component documentation at http://camel.apache.org/http4.
> Under "Setting up SSL for HTTP Client", the "Programmatic configuration of the component" example shows setting the SSLContextParameters of the http4 component instead of the correct https4 component.
> It might also be helpful to give an example of using the SSLContextParameters to force https4 to use a specific protocol, such as SSLv3. Notably, the underlying Apache HttpClient 4.x does not respect the Java environment variable "https.protocols", the only way I was able to successfully force SSLv3 in my case was by configuring the SSLContextParameters of the https4 component.
> My groovy spring DSL looks like this:
>     sslContextParams(SSLContextParameters) {
>         secureSocketProtocols = new SecureSocketProtocolsParameters().with { secureSocketProtocol.add('SSLv3'); it }
>         secureSocketProtocol = "SSLv3"
>     }
>     https4(org.apache.camel.component.http4.HttpComponent) {
>         connectionsPerRoute = 50
>         sslContextParameters = ref('sslContextParams')
>     }
> Note that setting SSLContextParameters.secureSocketProtocol alone is not sufficient, secureSocketProtocols also needs to be set (and I had hand-instantiate it as the list is not easily constructable via Spring - for me at least).


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)