camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7260) Documentation Bug - HTTP4 Component Configuration
Date Sat, 01 Mar 2014 06:59:19 GMT


Claus Ibsen commented on CAMEL-7260:

If you want to help with documentation, then please read this page

And send an ICLA to Apache, and then we can grant you edit rights to the documentation.

> Documentation Bug - HTTP4 Component Configuration
> -------------------------------------------------
>                 Key: CAMEL-7260
>                 URL:
>             Project: Camel
>          Issue Type: Task
>          Components: camel-http4, documentation
>            Reporter: Stephen Swensen
>            Priority: Trivial
> There is a bug in the HTTP4 component documentation at
> 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

View raw message