Hi, I'm writting because I'm trying to attack an endpoint with different SSL configurations (same endpoint, different configs each time). I have tried with some approaches but I don´t know if they are the best, because I'm facing some problems.
The approach that have worked the best for now is defining my own HttpClient and using a producer template to force a configuration of the client each time the endpoint is called. All the possible configurations (only a few) are defined in a spring configuration file with all the keystores and so. In my route, I retrieve an HttpEndpoint like this: HttpEndpoint httpEndpoint = (HttpEndpoint) CamelContextHelper.getMandatoryEndpoint(camelContext, endpointUri); And after that, when using the send method of the producer template (camel context), I have seen that the HttpProducer uses the method endpoint.createHttpClient() that configures the HttpClient , so the appropiate configuration is set and registered. But this configuration is set each time the endpoint is called. (All this with camel-http) I have also tried using a sslContextParametersRef with http4, but this way I end loosing the SSL configuration. (Once a configuration of a sslContextParametersRef have been overwritten, that configuration won´t be available anymore) I don´t know if my first approach (which doesn´t support concurrency) would be the good one of if there are other possibilities. Thanks in advance. Aida. Additional info: Using camel version 2.9.1 (I have seen that the 2.10 RC will be soon but using this one until 2.10 release) -- View this message in context: http://camel.465427.n5.nabble.com/HTTP-Atacking-to-the-same-endpoint-with-different-SSL-configurations-tp5715394.html Sent from the Camel - Users mailing list archive at Nabble.com.