AxiosError: unexpected end of file

[atulmy]

Describe the bug

AxiosError: unexpected end of file

Was not present before 1.2.1

To Reproduce

No response

Code snippet

No response

Expected behavior

No response

Axios Version

1.2.1

Adapter Version

No response

Browser

No response

Browser Version

No response

Node.js Version

No response

OS

No response

Additional Library Versions

No response

Additional context/Screenshots

No response

[atulmy]

Z_BUF_ERROR

[Flupster]

I've been having a similar issue downgrading to axios v1.2.0 will fix the problem

Something is broken with Brotli decompression and I think the culprit is somewhere in this merge #5306

An alternative if you don't want to downgrade right now is to force an encoding header with

axios.get("url", { 
    headers: { "Accept-Encoding": "gzip,deflate,compress" } 
});

This should make the response use something other than the "br" brotli compression encoding

[Flupster]

Running it in a browser works fine, problem occurs running in nodejs
Some reproduceable code:

const axios = require("axios");

axios
  .get("https://www.speedwaymotors.com/", { headers: { "Accept-Encoding": "br" } })
  .then((response) => console.log(response.data.length))
  .catch((error) => console.error(error));

cause: Error: unexpected end of file
      at BrotliDecoder.zlibOnError [as onerror] (node:zlib:189:17) {
    errno: -5,
    code: 'Z_BUF_ERROR'
  }

From a quick look I think newer versions of the Kestrel web server are compressing it differently? but curl handles it correctly

pinging @DigitalBrainJS and @jasonsaayman as this is big problem and should implement fix quick or remove v1.2.1 until it's production ready

changing https://github.com/axios/axios/blob/v1.x/lib/adapters/http.js#L430

from: streams.push(zlib.createBrotliDecompress(zlibOptions));
to: streams.push(zlib.createBrotliDecompress());

Fixes the problem

[robwilkes]

1.2.0 does indeed resolve the unexpected end of file exception, however the response data has weird encoding.
I've reverted to 1.1.3 and the response data is instead utf-8 / HTML. Seems 1.2.X is not ready for use.

[robutex]

We have the same problem as @robwilkes: we just tried to upgrade from 1.1.3 to 1.2.1 and we got the "unexpected end of file" error thrown by the brotli decompression. We are calling a .NET 6 API from NodeJs using Axios. Version 1.1.3 works ok, 1.2.0 returns something unusable and 1.2.1 throws the error. @Flupster might be right with the Kestrel part.

[kazazor]

Same here, got the problem with 1.2.1 when using the get function.
Actually, also in 1.2.0 something is not right here and we get everything mapped to undefined.
Works fine with 1.1.3 and 1.2.0-alpha.1

[TareHimself]

I get it while I am doing processing with an FFmpeg spawn process and a request is made with Axios, downgrading to 1.13 seems to fix it

[TomFrankly]

Same problem, even with an incredibly simple call:

const axios = require('axios')

async function getBulbasaur() {
  await axios.get(`https://pokeapi.co/api/v2/pokemon/1`).then((poke) => {

      console.log(poke.data.species.name)
      
    }).catch((err) => {
      console.log(err)
  })
}

getBulbasaur()

This works flawlessly on 1.1.3

Broken on 1.2.0 due to the content-header problem, broken now on 1.2.1 due to this "unexpected end of file" error.

[alisson-acioli]

I just ran into this issue with version 1.2.1. Do you have a fix planned?

[robert-calvert]

I was pulling my hair out getting the Z_BUF_ERROR thrown by Axios for otherwise successful POST requests to an external API for my Node project.

Downgrading to 1.1.3 resolved the issue.

[atulmy]

This is actually third time (most of any open source library) axios broke all my production apps 😢

[AndresAusecha]

Hello

I am getting this error by trying to fetch a plain text file. Really weird

[elvisun]

I'm puzzled on how consecutive bad versions got released on such a popular library, are there more tests we could help add to prevent these?

[AndresAusecha]

I'm puzzled on how consecutive bad versions got released on such a popular library, are there more tests we could help add to prevent these?

I think we can try to get a stream from Axios response when you are not supposed to get JSON, and then process that stream. At least for me that workaround worked fine

[InspectorGadget]

It works after I downgraded to 0.x. There is something going on in the newer versions (EG: 1.2.1).

[ShueiYang]

looks like the issue is still ongoing when i try to use Axios for the 1st time, I guess I will go back to the vanilla fetch method.

[ibrahiem9]

This is still an issue for me, quite surprising to see no resolution despite the module's popularity

[stephenwade]

This was fixed in v1.2.2.