Duplicate Content-Length and Content-Type headers in http response
(Doc ID 1610560.1)
Last updated on FEBRUARY 05, 2019
Applies to:Siebel CRM - Version 220.127.116.11  and later
Information in this document applies to any platform.
On : 18.104.22.168  version
Workflows are invoked by means of inbound HTTP requests as described at
Invoking a Workflow using the HTTP Inbound Transport in Siebel version 7.5.3 and above (Doc ID 477604.1)
It was noticed that some of the responses had duplicate HTTP headers, such as content-length or content-type.
The value of the headers was not necessarily the same.
In support´s own tests :
content-length was output only once, but was echoing the value from the request/input instead of showing a system calculated value that accurately reflects the size of the response/output payload.
content-type was output twice. Once with a value echoed from the input and a second time with a value calculated by the system.
In customer´s environment:
content-length header was output twice. Once echoing the value present in the request, the other with the correctly calculated value for the response.
Headers such as content-length and content-type should be automatically calculated by the application and set in the response only once.
Implement a call to a workflow as described at 477604.1
Call it from a client that sets HTTP headers content-length and content-type.(e.g call from SOAPUI).
Monitor the output and notice headers may appear twice or with an incorrect value.
The issue has the following business impact:
Due to this issue, the integration breaks as the caller can not understand the response.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document