Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Multiple incoming REST headers with the same name are not parsed

SA-56126

Summary



A REST connector with multiple Set-Cookie instances in a response has each instance setting a different cookie. Mapping the response to a Text property results in the second instance of the Set-Cookie overwriting the first instance. As a result, the property only contains the second instance.


Error Messages



Not Applicable


Steps to Reproduce



Invoke a REST connector which receives a response with multiple instances of the same header.


Root Cause



As the system maps response headers as a key-value pairing, only the last value of the header is received from the response and mapped to the specified property.


Resolution



An enhancement request, FDBK-26004, is created for consideration by Pega Product Management.


 

Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us