You would like to send custom HTTP Header to the target API, e.g., the custom HTTP headers like "Authorization", "Content-Type", etc., that created in Content Modifier step.
However even if the headers' values are generated successfully, but in runtime HTTP adapter is not sending these headers out.
You can check the HTTP trace from target API server to verify it.
A typical example is that, once custom "Authorization" or "x-csrf-token" header is missing, the target API will response HTTP 401 or 403 code.
Another situation could be, even though you notice the correct header value is generated before HTTP receiver adapter, but target API still complain the header is missing.
- SAP Cloud Integration
- SAP Integration Suite
CPI, Cloud Platform Integration, HCI, HANA Cloud Integration, HTTP header, parameter, value, Allowed Header, expression, Runtime Configuration, iFlow, Integration Flow, request, response, SOAP, HTTP, adapter, sender, endpoint, endpoint URL, SAP Cloud Platform Integration, SAP Cloud Integration, 401, 403, header is missing , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.