Troubleshooting
Problem
A RawRequest HTTP Post from SBI to IIS fails with 400 Bad Request (Invalid Header Name)
Symptom
A document containing custom HTTP headers was generated and posted with RawRequest set to true in the HTTP Client Post service.
The document could be successfully posted from a different client, but posting with the HTTP Client Adapter was causing partners' IIS web servers to return "400 Bad Request (Invalid Header Name)" as a response. Posting the document to an HTTP Server adapter with the same HTTP client adapter configuration was successful.
[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Adapters","Platform":[{"code":"PF027","label":"Solaris"}],"Version":"5.2;5.2.1;5.2.2;5.2.3;5.2.4;5.2.4.1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21657447