Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
2.21.0
-
None
-
None
-
Patch Available
-
Unknown
-
Patch
Description
It seems the problem still persists.. there were two determineheaders methods as i just noticed now. And your fix is implemented in the Abstractclientbase class, determineheaders method. However, i noticed during runtime that the method determineheaders in the interface SalesforceProcessor is being called instead.
Therefore currently the problem still persists.
Attachments
Attachments
Issue Links
- is a child of
-
CAMEL-12085 Don't mandate header case for custom Salesforce HTTP haders
- Resolved