davsclaus opened a new issue, #3244:
URL: https://github.com/apache/camel-kamelets/issues/3244

   `http-sink` sends the headers of the message as HTTP headers, and that 
includes an `Authorization` or `Proxy-Authorization` header that is already on 
the message. Two cases where that is not what the flow wants:
   
   - Behind a source that turns request headers into message headers, such as 
`webhook-source`, the credential of the caller is sent on to the service that 
`http-sink` calls.
   - When `http-sink` has its own login configured 
(`authUsername`/`authPassword` with `authenticationPreemptive`, or 
`authBearerToken`), the header of the message is sent instead of that login, as 
the HTTP client does not add its own header when the request already has one.
   
   Change: `http-sink` removes the `Authorization` and `Proxy-Authorization` 
headers of the message before the call, as it already does for the headers that 
choose the address, so the login comes only from its options. A flow that sets 
a different token for each message can use the `http` component directly. To be 
added to the upgrade notes (#3190).
   
   _Claude Code on behalf of Claus Ibsen_
   


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