Malformed response causing odd failure with no error

[kjs3]

Describe the bug

• Node.js version: 14.12.0 & 15.2.1
• OS & version: MacOS Catalina (10.15.7) & Manjaro (rolling release, up to date)

I stumbled on a silent failure when parsing a bunch of podcast feeds. Specifically this one.

Chrome fails with a net::ERR_CONTENT_DECODING_FAILED error.
Curl and the Axios lib seem to handle the response just fine.

Actual behavior

Silent failure. The promise doesn't seem to resolve at all. I'm not sure what's going on within the Node loop.

Expected behavior

A ResponseError is probably the right behavior. The fact that some other libs can handle this confuses the issue though.

Code to reproduce

// got-test.js
const got = require('got')

main()

async function main() {
  const url = 'https://read.audioarchitect.co/feed/podcast'

  try {
    console.log('getting: ', url)
    const res = await got(url)
    console.log('never here: ', res)
  } catch (err) {
    console.error(err)
    console.log('never here either')
  }
}

node got-test.js

Checklist

• I have read the documentation.
• I have tried my code with the latest version of Node.js and Got.

[szmarczak]

Good catch!

[szmarczak]

This is caused by nodejs/node#34350 - unfortunately Node.js has marked this as wontfix, so we have to make a workaround for this...

[szmarczak]

Duplicate of #1357 - need to check if it's still in the tests

[szmarczak]

Yes, we still have this in the tests. Looks like this is a different variation but the error is ParseError as well.

[szmarczak]

curl https://read.audioarchitect.co/feed/podcast -H 'accept-encoding: gzip, deflate, brotli' -v --http1.1 --ignore-content-length

[szmarczak]

@sindresorhus I'm really looking forward to undici. The native Node.js parser is giving me headaches.