Service Callout headers

Google Cloud Apigee
1

Hi,

We found a bug, we think in the Service Callout policy:

  1. Create proxy

  2. Put Service callout to call external API

2.1 use true flag inside Callout

  1. Transfer from client side any header with values splitter by commas: header-name: a,b

As a result, Service Callout will send to this API duplicate headers:

header-name: a

header-name: b

In some cases, backend will die because of this - some backends know to aggregate the headers in to one, with multiple values, some - not.

We opened ticket for that, but I wanted to ask community what in their opinion are the best and most efficient workaround on this.

-D

2

This we have experienced earlier in some reqyears.

We used request.header.name.values.string to get all in one header