Parses set-cookie header differently than superagent when run inside jest

[timwis]

Hi folks, I've got quite a peculiar bug that I've isolated in this repo. My server (koa) returns two set-cookie headers. When run standalone, both superagent and supertest parse the two set-cookie headers into separate items in an array.

node request.js

supertest [ 'koa:sess=foo; path=/; httponly',
  'koa:sess.sig=E3XmR2LMmP11O418i_oXS61zGi0; path=/; httponly' ]
superagent [ 'koa:sess=foo; path=/; httponly',
  'koa:sess.sig=E3XmR2LMmP11O418i_oXS61zGi0; path=/; httponly' ]

When run in the context of jest, supertest behaves differently, combining the two set-cookie headers.

npm test

superagent [ 'koa:sess=foo; path=/; httponly',
  'koa:sess.sig=E3XmR2LMmP11O418i_oXS61zGi0; path=/; httponly' ]
supertest [ 'koa:sess=foo; path=/; httponly,koa:sess.sig=E3XmR2LMmP11O418i_oXS61zGi0; path=/; httponly' ]

The repo has a reproduction. Any idea how this could be happening? Am I crazy?

[crux153]

There seems to be an issue with jest. See #413 and jestjs/jest#3547, jestjs/jest#2549