Dmitriy Mozgovoy

Results 118 comments of Dmitriy Mozgovoy

> It might be challenging to provide a publicly accessible test case since finding APIs that reliably respond with a 204 status code could be difficult. I can't reproduce ```js...

Axios (XMLHttpRequest) cannot get the status code if: - a network error has occurred (on TCP/IP layer) - browser prevented JS from reading the request due to cross-domain request policy...

Default adapter setting: `{adapter: ['xhr', 'http']}` Axios is trying to use the first adapter available, so if you're getting this error it means your environment doesn't support both `xhr` and...

You can try the new beta, which has added the fetch adapter, but there is no guarantee of compatibility with the Edge Runtime. ``` npm i axios@next ```

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

> Is there a technical reason for it? CORS specification. The short answer is that the JS environment is not allowed to see the real cause of the error. Here's...

Axios supports Node v12 and above, so we can't just go the easy way and use the latest built-ins but have to support different formData implementations, as Axios is designed...

> 20.12.0 > 18.18.2 I can't reproduce the issue using your example in both versions. Have you tested this on your example?

The `lengthComputable` field has been re-added in the new beta, although it doesn't make much sense since it simply checks if `total` != null.

Axios v1 encodes nested objects in [qs style](https://www.npmjs.com/package/qs), not as JSON string. Unfortunately qs [does not support](https://github.com/ljharb/qs/issues/362) serializing a nested object with an empty structure and there is no specification...