davsclaus opened a new pull request, #3252:
URL: https://github.com/apache/camel-kamelets/pull/3252

   Fixes #2042, as oscerd suggested there (option 1).
   
   `cookieManagementDisabled` is an option of the `http` component, not of the 
endpoint, so a Kamelet cannot take it as an option: given on the endpoint, it 
would only be sent to the service as a query parameter. Instead, the `Good to 
know:` paragraph of `http-sink` and `http-source` now says:
   
   > It keeps the cookies that the service sets, as a browser does, and sends 
them back on the next calls. To turn that off, set the application property 
`camel.component.http.cookie-management-disabled=true`, or 
`camel.component.https.cookie-management-disabled=true` for an `https://` 
address: it then applies to every call of the application to such addresses.
   
   ### Checked by running
   With `camel run` (Camel 4.24.0-SNAPSHOT), `http-sink` and `http-source` 
called a local server that answers with `Set-Cookie: session=abc123` and logs 
the `Cookie` header of each request:
   
   | Address | Application property | Requests with the cookie |
   |---|---|---|
   | `http://` | none | all after the first |
   | `http://` | `camel.component.http.cookie-management-disabled=true` | none |
   | `https://` | none | all after the first |
   | `https://` | `camel.component.http.cookie-management-disabled=true` | all 
after the first: the `http` property does not apply |
   | `https://` | `camel.component.https.cookie-management-disabled=true` | 
none |
   
   Only the two descriptions change. `./mvnw clean install` regenerated the 
library copy and the index, and passes.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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