CLM Workflow - HTTPS Client Step - Multiple cookies in response headers

I’m trying to develop a custom integration between DocuSign CLM and one of our internal applications. I have DocuSign communicating with a few API calls through a set of load-balanced servers past our firewall.

During this interaction, I must keep track of which of our servers I began the communication with. This is done with cookies given back to me through the initial authorization call: one from the server and one from the firewall. Both are returned as Set-Cookie response headers.

In my DocuSign CLM workflow, I use the HTTPS Client Step to make my API calls and I have the response headers being put into a variable. The issue I’m running into is that DocuSign seems to save one of the Set-Cookie headers but not the other one. It just seems to save whichever it sees first.

Is there a way I can save both of these Set-Cookie response headers when I make an API call using the HTTPS Client Step? Thanks!