Croway opened a new pull request, #30081:
URL: https://github.com/apache/camel/pull/30081

   - **`sslContextParameters` descriptions** (`HttpComponent`, `HttpEndpoint`) 
said only one `SSLContextParameters` instance is supported per `HttpComponent` 
(the endpoint one also named the old `org.apache.camel.util.jsse` package). 
`HttpComponent.createEndpoint()` resolves `sslContextParameters` per endpoint 
(endpoint, then component, then global for `https`) and builds a connection 
manager per endpoint with it, so endpoints of one component can use different 
instances. The descriptions now say so; regenerated component descriptors, 
catalog and component/endpoint DSL.
   - **"Using different SSLContextParameters"** said the same and showed one 
component per instance. It now says the endpoint option takes precedence, shows 
a `toD` with `sslContextParameters=#mySSL` (Java, YAML), links to defining 
`SSLContextParameters` in XML/YAML, shows `camel.ssl.*` with 
`camel.component.https.use-global-ssl-context-parameters=true`, and notes that 
a `clientConnectionManager` on the component or endpoint is used as it is 
(`createConnectionManager()` returns it before applying SSL).
   - **"Configuring Apache HTTP Client Directly"** showed HttpClient 4 
`SchemeRegistry`/`SSLSocketFactory` code to set a key store and trust store. 
That API is not in HttpClient 5; the text now points to `sslContextParameters` 
for that case.
   - **"Using System Properties"**: added `https.proxyHost`/`https.proxyPort` 
(HttpClient's system route planner uses them for `https` targets; 
`http.proxyHost` only applies to `http` targets), removed `http.maxConnections` 
(HttpClient 5 does not read it, and Camel sets its own connection manager), and 
explained that without `useSystemProperties` only the JVM default trust store 
applies (`SSLContexts.createDefault()` vs `createSystemDefault()` in 
`HttpComponent.createTlsStrategy()`), plus the component-level 
`camel.component.http(s).use-system-properties=true`.
   - **"Using proxy settings outside of URI"** said Camel first applies the 
Java system properties or CamelContext global options, then the endpoint proxy 
options. `HttpEndpoint.createHttpClient()` reads the global options only when 
`useSystemProperties` is false, and the JVM proxy properties only when it is 
true; the endpoint and component proxy options are applied afterwards and win.
   
   _Claude Code on behalf of Federico Mariani_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to