I eventually stumbled across a PR that addresses this issue (https://github.com/oesmith/puffing-billy/pull/167) by setting the accept-encoding header to a blank string instead of deleting it. According to @damned, the root cause is the em-http-request library which sets the accept-encoding header if it's not present. Once I made this change, the Content-decoder error disappeared.
ronwsmith
commented
5 years ago
I was experiencing the same issue as in https://github.com/oesmith/puffing-billy/issues/204 which seems to be due to puffing billy being unable to decode a response.
I eventually stumbled across a PR that addresses this issue (https://github.com/oesmith/puffing-billy/pull/167) by setting the
accept-encodingheader to a blank string instead of deleting it. According to @damned, the root cause is theem-http-requestlibrary which sets theaccept-encodingheader if it's not present. Once I made this change, theContent-decodererror disappeared.