fix: Properly forward headers in asset cache

CDP returns multiple headers joined by newlines, however `request.respond` (used
for cached responses) will hang if there are newlines in headers. This commit
normalizes header values as arrays split on newlines.

src/utils/response-cache.ts

@@ -34,7 +34,15 @@ export async function cacheResponse(response: Response, logger: any) {
 
     responseCache[responseUrl] = {
       status: response.status(),
-      headers: response.headers(),
+      // CDP returns multiple headers joined by newlines, however
+      // `request.respond` (used for cached responses) will hang if there are
+      // newlines in headers. The following reduction normalizes header values
+      // as arrays split on newlines
+      headers: Object.entries(response.headers())
+        .reduce((norm, [key, value]) => (
+          // tslint:disable-next-line
+          Object.assign(norm, { [key]: value.split('\n') })
+        ), {}),
       body: buffer,
     }
 

test/unit/utils/response-cache.test.ts

@@ -67,4 +67,15 @@ describe('Response cache util', () => {
 
     expect(getResponseCache('http://example.com/foo.txt')).to.eql(undefined)
   })
+
+  it('newlines are removed from headers', async () => {
+    await cacheResponse({
+      ...defaultResponse,
+      headers: () => ({ 'fake': 'foo=bar\nthing=baz' })
+    }, logger)
+
+    expect(getResponseCache('http://example.com/foo.txt').headers).to.eql({
+      fake: [ 'foo=bar', 'thing=baz' ],
+    })
+  })
 })