KB Article #177029
Content-Type HTTP header is duplicated when using ICAP Filter
Problem
Response back from API Gateway contains duplicate HTTP Content-Type header when calling ICAP filter.
e.g.
Content-Type: application/soap+xml;charset=UTF-8;action="http://schemas.gov.ie/ndesk/newService/GetNodes"
Content-Type: application/soap+xml; action="http://schemas.gov.ie/ndesk/newService/GetNodes"; charset="UTF-8"
Workaround
1. Call "Retrieve from HTTP header" to save the original value of Content-Type to an attribute content.type.header. At this time there is only one Content-Type.
2. Invoke ICAP server with ICAP filter - there are two Content-Type headers after this filter is executed.
3. Call "Remove HTTP Header" for Content-Type header. This actually removes both Content-Type headers.
4. Call "Add HTTP Header" to add new Content-Type header initialized with the value of ${content.type.header} attribute.
The client receives the Content-Type only once when this procedure is followed.
Fix
The bug will be addressed in 7.3.1 SP3. There is no current ETA yet for SP3. This will updated here when available.