how to request.respond() multiple set-cookie headers?

[ghost]

If I look at the respond code int NetworkManager.js it only accepts a single 'set-cookie' header as a string.

  async respond(response) {
    /** @type {!Object<string, string>} */
    const responseHeaders = {};
    if (response.headers) {
      for (const header of Object.keys(response.headers))
        responseHeaders[header.toLowerCase()] = response.headers[header];
    }
    if (response.contentType)
      responseHeaders['content-type'] = response.contentType;
    if (responseBody && !('content-length' in responseHeaders))
      responseHeaders['content-length'] = String(Buffer.byteLength(responseBody));

I've tried

{headers: {'set-cookie': '1=1.;Domain=.site.com;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Priority=HIGH,2=2.;Domain=.site.com;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Secure;HttpOnly;Priority=HIGH;SameSite=none,3=3.;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Secure;HttpOnly;Priority=HIGH'}}

and

{headers: {'set-cookie': '1=1.;Domain=.site.com;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Priority=HIGH, 2=2.;Domain=.site.com;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Secure;HttpOnly;Priority=HIGH;SameSite=none, 3=3.;Path=/;Expires=Tue, 26-Apr-2022 10:30:53 GMT;Secure;HttpOnly;Priority=HIGH'}}

but neither set the cookies

If I mock request.respond and put the set-cookie each on their own header it works.

[Ganitzsh]

I have a similar issue, did you find a solution to this?

[ghost]

I have a similar issue, did you find a solution to this?

I think I mocked request.respond with my own implementation. it's been a while, don't have the code anymore.

[onlyil]

I have a similar issue, did you find a solution to this?

[dukei]

Any progress on this issue? It is still not possible to pass multiple set-cookie headers to request.respond().

[Junyan]

@dukei @onlyil @dukei The issue is solved, see v13.6.0.

[stale]

We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.

[stale]

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!