API Connect Gateway should parse HTTP Headers into a predictable format to ensure

Parsing into a predictable format ensures that any code and / or logging is predictable, enabling, for example - accurate, repeatable, concise Analytics / logging filters to be applied to header values.

The current APIC behaviour leads to a variety of header values being received / logged, for key HTTP headers this may lead to examples such as:

X-Consumer-Correl-ID

X-Consumer-Correl-Id

x-consumer-correl-id

X-CONSUMER-CORREL-ID

...being logged (across a variety of API clients; APIC, ACE, cURL, etc), making it difficult to write predictable Analytics / logging filters in tools such a Elastic stack.

Parsing into a predictable format would ensure consistency with other integration products within the same product family / Cloud Pak e.g. App Connect Enterprise, which parses / cleanses HTTP Header values into an Upper-Camel-Kebab case scheme.

Previously for the IBM App Connect Enterprise (ACE) product line (PMR 45754,001,866) IBM explained that the HTTP standard stipulates that Applications should be case-insensitive to HTTP Header elements, and ACE is converting the inbound HTTP Header (intentionally) when a message is parsed into a Message Flow so that the Header is converted to a "predictable" format regardless of what case the Service Consumer used to provide the header elements. This behaviour offers a strategic advantage and being intentional