Axios catch error 400 - Исправление ошибок и поиск оптимальных решений проблем

I’m trying to understand javascript promises better with Axios. What I pretend is to handle all errors in Request.js and only call the request function from anywhere without having to use catch().

In this example, the response to the request will be 400 with an error message in JSON.

This is the error I’m getting:

Uncaught (in promise) Error: Request failed with status code 400

The only solution I find is to add .catch(() => {}) in Somewhere.js but I’m trying to avoid having to do that. Is it possible?

Here’s the code:

Request.js

export function request(method, uri, body, headers) {
  let config = {
    method: method.toLowerCase(),
    url: uri,
    baseURL: API_URL,
    headers: { 'Authorization': 'Bearer ' + getToken() },
    validateStatus: function (status) {
      return status >= 200 && status < 400
    }
  }

  ...

  return axios(config).then(
    function (response) {
      return response.data
    }
  ).catch(
    function (error) {
      console.log('Show error notification!')
      return Promise.reject(error)
    }
  )
}

Somewhere.js

export default class Somewhere extends React.Component {

  ...

  callSomeRequest() {
    request('DELETE', '/some/request').then(
      () => {
        console.log('Request successful!')
      }
    )
  }

  ...

}

asked Apr 22, 2018 at 15:45

Actually, it’s not possible with axios as of now. The status codes which falls in the range of 2xx only, can be caught in .then().

A conventional approach is to catch errors in the catch() block like below:

axios.get('/api/xyz/abcd')
  .catch(function (error) {
    if (error.response) {
      // Request made and server responded
      console.log(error.response.data);
      console.log(error.response.status);
      console.log(error.response.headers);
    } else if (error.request) {
      // The request was made but no response was received
      console.log(error.request);
    } else {
      // Something happened in setting up the request that triggered an Error
      console.log('Error', error.message);
    }

  });

Another approach can be intercepting requests or responses before they are handled by then or catch.

axios.interceptors.request.use(function (config) {
    // Do something before request is sent
    return config;
  }, function (error) {
    // Do something with request error
    return Promise.reject(error);
  });

// Add a response interceptor
axios.interceptors.response.use(function (response) {
    // Do something with response data
    return response;
  }, function (error) {
    // Do something with response error
    return Promise.reject(error);
  });

answered Aug 9, 2018 at 13:26

Plabon DuttaPlabon Dutta

6,5493 gold badges29 silver badges32 bronze badges

If you want to gain access to the whole the error body, do it as shown below:

 async function login(reqBody) {
  try {
    let res = await Axios({
      method: 'post',
      url: 'https://myApi.com/path/to/endpoint',
      data: reqBody
    });

    let data = res.data;
    return data;
  } catch (error) {
    console.log(error.response); // this is the main part. Use the response property from the error object

    return error.response;
  }

}

answered Mar 24, 2020 at 5:22

elonaireelonaire

1,7681 gold badge9 silver badges16 bronze badges

You can go like this:
error.response.data
In my case, I got error property from backend. So, I used error.response.data.error

My code:

axios
  .get(`${API_BASE_URL}/students`)
  .then(response => {
     return response.data
  })
  .then(data => {
     console.log(data)
  })
  .catch(error => {
     console.log(error.response.data.error)
  })

answered Mar 26, 2020 at 14:08

If you wan’t to use async await try

export const post = async ( link,data ) => {
const option = {
    method: 'post',
    url: `${URL}${link}`,
    validateStatus: function (status) {
        return status >= 200 && status < 300; // default
      },
    data
};

try {
    const response = await axios(option);
} catch (error) {
    const { response } = error;
    const { request, ...errorObject } = response; // take everything but 'request'
    console.log(errorObject);
}

Ben T

4,4663 gold badges21 silver badges22 bronze badges

answered Oct 16, 2019 at 15:59

user4920718user4920718

1,0351 gold badge9 silver badges12 bronze badges

I tried using the try{}catch{} method but it did not work for me. However, when I switched to using .then(...).catch(...), the AxiosError is caught correctly that I can play around with. When I try the former when putting a breakpoint, it does not allow me to see the AxiosError and instead, says to me that the caught error is undefined, which is also what eventually gets displayed in the UI.

Not sure why this happens I find it very trivial. Either way due to this, I suggest using the conventional .then(...).catch(...) method mentioned above to avoid throwing undefined errors to the user.

Dharman♦

29.3k21 gold badges80 silver badges131 bronze badges

answered Feb 2, 2021 at 8:02

For reusability:

create a file errorHandler.js:

export const errorHandler = (error) => {
  const { request, response } = error;
  if (response) {
    const { message } = response.data;
    const status = response.status;
    return {
      message,
      status,
    };
  } else if (request) {
    //request sent but no response received
    return {
      message: "server time out",
      status: 503,
    };
  } else {
    // Something happened in setting up the request that triggered an Error
    return { message: "opps! something went wrong while setting up request" };
  }
};

Then, whenever you catch error for axios:

Just import error handler from errorHandler.js and use like this.
  try {
    //your API calls 
  } catch (error) {
    const { message: errorMessage } = errorHandlerForAction(error);
     //grab message
  }

answered Jan 12, 2022 at 15:51

If I understand correctly you want then of the request function to be called only if request is successful, and you want to ignore errors. To do that you can create a new promise resolve it when axios request is successful and never reject it in case of failure.

Updated code would look something like this:

export function request(method, uri, body, headers) {
  let config = {
    method: method.toLowerCase(),
    url: uri,
    baseURL: API_URL,
    headers: { 'Authorization': 'Bearer ' + getToken() },
    validateStatus: function (status) {
      return status >= 200 && status < 400
    }
  }


  return new Promise(function(resolve, reject) {
    axios(config).then(
      function (response) {
        resolve(response.data)
      }
    ).catch(
      function (error) {
        console.log('Show error notification!')
      }
    )
  });

}

answered Feb 10, 2021 at 22:19

Damir MiladinovDamir Miladinov

1,0741 gold badge10 silver badges15 bronze badges

https://stackabuse.com/handling-errors-with-axios/

    let res = await axios.get('/my-api-route');

    // Work with the response...
} catch (err) {
    if (err.response) {
        // The client was given an error response (5xx, 4xx)
    } else if (err.request) {
        // The client never received a response, and the request was never left
    } else {
        // Anything else
    }
}

try {
    let res = await axios.get('/my-api-route');

    // Work with the response...
} catch (err) {
    if (err.response) {
        // The client was given an error response (5xx, 4xx)
    } else if (err.request) {
        // The client never received a response, and the request was never left
        console.log(err.request);
    } else {
        // Anything else
    }
}

answered Jun 6, 2022 at 7:50

call the request function from anywhere without having to use catch().

First, while handling most errors in one place is a good Idea, it’s not that easy with requests. Some errors (e.g. 400 validation errors like: «username taken» or «invalid email») should be passed on.

So we now use a Promise based function:

const baseRequest = async (method: string, url: string, data: ?{}) =>
  new Promise<{ data: any }>((resolve, reject) => {
    const requestConfig: any = {
      method,
      data,
      timeout: 10000,
      url,
      headers: {},
    };

    try {
      const response = await axios(requestConfig);
      // Request Succeeded!
      resolve(response);
    } catch (error) {
      // Request Failed!

      if (error.response) {
        // Request made and server responded
        reject(response);
      } else if (error.request) {
        // The request was made but no response was received
        reject(response);
      } else {
        // Something happened in setting up the request that triggered an Error
        reject(response);
      }
    }
  };

you can then use the request like

try {
  response = await baseRequest('GET', 'https://myApi.com/path/to/endpoint')
} catch (error) {
  // either handle errors or don't
}

answered Feb 24, 2020 at 12:35

David SchumannDavid Schumann

12.7k8 gold badges70 silver badges89 bronze badges

One way of handling axios error for response type set to stream that worked for me.

.....
.....
try{
   .....
   .....
   // make request with responseType: 'stream'
   const url = "your url";
   const response = axios.get(url, { responseType: "stream" });
   // If everything OK, pipe to a file or whatever you intended to do
   // with the response stream
   .....
   .....
} catch(err){
  // Verify it's axios error
  if(axios.isAxios(err)){
    let errorString = "";
    const streamError = await new Promise((resolve, reject) => {
      err.response.data
        .on("data", (chunk) => {
           errorString += chunk;
          }
        .on("end", () => {
           resolve(errorString);
         }
      });
    // your stream error is stored at variable streamError.
    // If your string is JSON string, then parse it like this
    const jsonStreamError = JSON.parse(streamError as string);
    console.log({ jsonStreamError })
    // or do what you usually do with your error message
    .....
    .....
  }
  .....
  .....
}

answered Oct 10, 2021 at 8:58

BikashBikash

1601 silver badge6 bronze badges

If I understand you correctly, you want some kind of global handler, so you don’t have to attach a catch handler to every request you make. There is a window event for that called unhandledrejection.

You can read more about this Event in the official documentation: https://developer.mozilla.org/en-US/docs/Web/API/Window/unhandledrejection_event

Here is how you can attach a listener for this Event:

window.addEventListener('unhandledrejection', (event) => {
  // Handle errors here...
});

answered Dec 1, 2022 at 9:15

DavidDavid

516 bronze badges

Источник

If you have been searching the web for some information about AXIOS error messages, and would like to understand how to use them, then you have come to the right place.

TLTR; Find the code snippets in the following section

If you search the web on this topic, all you can find is:

catching error body using axios post
Unable to catch the body of error
JS Axios – how to get response body in event of error?
How to see axios error response JSON in React

The list could have gone on and on, but they all ask for the sample simple question:

How can someone get the actual error information coming from a bad request made with AXIOS.

In this post we are going to provide information on “why” so many people ask for information, and “how” this information can be found.

Why so many people ask for this

If you have ever worked with an api, you perfectly know that request not always go to plan. You hope to always get a lovely response with a status of 200, but this does not always happens.

In many instances the status of our request may return some kind of error (400, 500), and when this happens we would like to be able to have a readable error message.

axios.get('EndpointWithAuthorizedError')
    .then((response) => {})
    .catch((error) => {
        console.log(error);
    })

Enter fullscreen mode

Exit fullscreen mode

Unfortunately if the above would ever fail with a meaningful error, we would still see this within our console, as the variable passed by the catch statement seem to be of type “string”.

Error: Request failed with status code 401

Enter fullscreen mode

Exit fullscreen mode

This is actually the main reason why so many people are “forced” to ask for help.

How can we process AXIOS error message

There is actually no magic when processing the error messages. In fact, the catch is in the fact that the variable received by the catch statement seem to be a string, but in reality it is not.

The AXIOS error message can actually return 3 different structure, depending from what kind of failure it has (crazy right… I thought that too).

Error in setting up the request

This error can happen if we have made an actual mistake in setting up the AXIOS request. It could be something with the data passed, or a configuration setting.

When this happen we can actually find the information we need by accessing the message parameter of the catch.

axios.get('wrongSetup')
    .then((response) => {})
    .catch((error) => {
        console.log(error.message);
    })

//or using destructuring
axios.get('wrongSetup')
    .then((response) => {})
    .catch(({message) => {
        console.log(message);
    })

Enter fullscreen mode

Exit fullscreen mode

No response – Network Error

This scenario will take place when our request had no response at all. This can happen when the URL is incorrect, or if the receiving server is down.

When this happen we can access more information about our request bu accessing the request parameter. This will return the actual “request” information.

axios.get('network error')
     .then((response) => {})
     .catch((error) => {
         console.log(error. request );
     })
//or using destructuring
 axios.get('network error')
     .then((response) => {})
     .catch(({ request ) => {
         console.log( request );
     })

Enter fullscreen mode

Exit fullscreen mode

Request returned with an error status

This is one of the most common, or more specifically the one type of “error” that need to be manage to make sure our web applications function properly.

There are hundreds of status code differently than 200 (https://developer.mozilla.org/en-US/docs/Web/HTTP/Status), that would fit in this category. I am going to list below the most important:

400: Bad request
401: Unauthorized
403: Forbidden
404: Not Found
500: Internal Server error
502: Bad Gateway

When any of the above happen, we would like to know more about the request. In this case there are more information provided to us: data, status, header.

axios.get('errorStatus')
     .then((response) => {})
     .catch((error) => { 
         console.log(error.response.data);  
         console.log(error.response.status);  
         console.log(error.response.headers); 
     })

//or using destructuring
 axios.get('errorStatus')
     .then((response) => {})
     .catch(({ response }) => { 
         console.log(response.data);  
         console.log(response.status);  
         console.log(response.headers);  
     })

Enter fullscreen mode

Exit fullscreen mode

With the above code, we will be able to get all the information we need about the response to our request. These includes the status code, the header and last but not least the data that the server has sent with the request.

When using any kind of API, the data parameter is going to include essential information, usually used for development purposes, but at times also good to show to the end users.

I hope to have saved you some time, and please feel free to comment, or provide suggestion to improve this post and help future readers

Источник

Содержание

(400) Bad Request. xhr 166, #2450
Comments
400 Bad Request Error #4513
Comments
Describe the issue
Example Code
Expected behavior, if applicable
Environment
Additional context/Screenshots
Footer

(400) Bad Request. xhr 166, #2450

At the moment, i am trying to post a request to the server but, it keeps telling me bad request. and i have rechecked my code through, and i do not know what the issue is. cos i am following a tutorial as a newbie in «react».

the error from my terminal reads.
SyntaxError: Unexpected token D in JSON at position 0
[0] at JSON.parse (),

the error from developer tools reads.
POST http://localhost:3000/api/users 400 xhr.js:166 (Bad Request)

dispatchXhrRequest	@	xhr.js:166
xhrAdapter	@	xhr.js:16
dispatchRequest	@	dispatchRequest.js:49
Promise.then (async)
request	@	Axios.js:56

Pls I need help.
below is the code taking from different folders. //

import React, < useReducer >from «react»;
import axios from «axios»;
import AuthContext from «./authContext»;
import authReducer from «./authReducer»;
import setAuthToken from «../../utils/setAuthToken»;
import <
REGISTER_SUCCESS,
REGISTER_FAIL,
USER_LOADED,
AUTH_ERROR,
LOGIN_SUCCESS,
LOGIN_FAIL,
LOGOUT,
CLEAR_ERRORS
> from «../types»;

const AuthState = props => <
const initialState = <
token: localStorage.getItem(«token»),
isAuthenticated: null,
loading: true,
user: null,
error: null
>;
const [state, dispatch] = useReducer(authReducer, initialState);

// Register User
const register = async formData => <
const config = <
headers: <
«Content-Type»: «application/json»
>
>;
try <
const res = await axios.post(«/api/users», formData, config);
dispatch( <
type: REGISTER_SUCCESS,
payload: res.data
>);
loadUser();
> catch (error) <
dispatch( <
type: REGISTER_FAIL,
payload: error.response.data.msg
>);
>
>;
// FROM MY AUTH REDUCER FOLDER:
import <
REGISTER_SUCCESS,
REGISTER_FAIL,
USER_LOADED,
AUTH_ERROR,
LOGIN_SUCCESS,
LOGIN_FAIL,
LOGOUT,
CLEAR_ERRORS
> from «../types»;

export default (state, action) => <
switch (action.type) <
case USER_LOADED:
return <
. state,
isAuthenticated: true,
loading: false,
user: action.payload
>;
case REGISTER_SUCCESS:
localStorage.setItem(«token», action.payload.token);
return <
. state,
. action.payload,
isAuthenticated: true,
loading: false
>;
case REGISTER_FAIL:
localStorage.removeItem(«token»);
return <
. state,
token: null,
isAuthenticated: false,
loading: false,
user: null,
error: action.payload
>;

// FROM MY ROUTE USERS FOLDER:
const express = require(«express»);
const router = express.Router();
const bcrypt = require(«bcryptjs»);
const jwt = require(«jsonwebtoken»);
const config = require(«config»);
// . rest of the initial code omitted for simplicity.
const < check, validationResult >= require(«express-validator»);

const User = require(«../models/User»);

//@route POST api/users
// @desc register a user
// @access Public
router.post(
«/»,
[
check(«name», «Name is required»)
.not()
.isEmpty(),
check(«email», «Please Include a Valid Email»).isEmail(),
check(
«password»,
«Please Enter Password with 5 or more characters»
).isLength(< min: 5 >)
],
async (req, res) => <
// Finds the validation errors in this request and wraps them in an object with handy functions
const errors = validationResult(req);
if (!errors.isEmpty()) <
return res.status(400).json(< errors: errors.array() >);
>
const < name, email, password >= req.body;
try <
let user = await User.findOne(< email >);
if (user) <
return res.status(400).json(< msg: «User Already Exists» >);
>
user = new User(< name, email, password >);
const salt = await bcrypt.genSalt(10);
user.password = await bcrypt.hash(password, salt);
await user.save();
const payload = <
user: <
id: user.id
>
>;
jwt.sign(
payload,
config.get(«jwtSecret»),
<
expiresIn: 360000
>,
(error, token) => <
if (error) throw error;
res.json(< token >);
>
);
> catch (error) <
console.error(error.message);
res.status(500).send(«Server Error»);
>
>
);

The text was updated successfully, but these errors were encountered:

Источник

400 Bad Request Error #4513

Describe the issue

I have developed an Discord AI Chatbot, everything worked just fine until now, the bot gives no response due to axios giving an 400 Bad Request error

Example Code

Code snippet to illustrate your question

Expected behavior, if applicable

The Bot is supposed to answer to the question with an random answer

Environment

Axios Version [e.g. 0.18.0]: 0.21.1
Adapter [e.g. XHR/HTTP]: HTTP
Browser [e.g. Chrome, Safari]: Opera GX
Browser Version [e.g. 22]: LVL3 (core: 83.0.4254.70)
Node.js Version [e.g. 13.0.1]: 16.13.1
OS: [e.g. iOS 12.1.0, OSX 10.13.4]: Windows 10
Additional Library Versions [e.g. React 16.7, React Native 0.58.0]

Additional context/Screenshots

Add any other context about the problem here. If applicable, add screenshots to help explain.

The text was updated successfully, but these errors were encountered:

What does this have to do with axios?

Just look at your API and figure out why it’s giving a 400

You’re probably missing your environnement variables or are not encoding the parameters

I’ve never had any problems with axios and the api but now its axios that keeps giving me an Code 400 Bad Request

No, it’s not axios, it’s the url you’re passing to it.

No, it’s not axios, it’s the url you’re passing to it.

How that? I’ve checked their documentation and I’m using the API Link provided

Okay look, this is not a support forum for people learning to code but an issue board for axios

Just do a console.log( http://api.brainshop.ai/get?bid=$&key=$&uid=$&msg=$ ‘) and you’ll get the url, paste it in the browser it’ll give you an HTTP error 400 because params are malformed. likely because you need to use encodeURIComponent on them before putting them in the URL or better yet use axios to correctly encode them

Error: Request failed with status code 400
at createError (C:Users DocumentsBotsBlockAInode_modulesaxioslibcorecreateError.js:16:15)
at settle (C:Users DocumentsBotsBlockAInode_modulesaxioslibcoresettle.js:17:12)
at IncomingMessage.handleStreamEnd (C:Users DocumentsBotsBlockAInode_modulesaxioslibadaptershttp.js:269:11)
at IncomingMessage.emit (node:events:402:35)
at endReadableNT (node:internal/streams/readable:1343:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21) <
config: <
url: ‘http://api.brainshop.ai/get’,
method: ‘get’,
headers: <
Accept: ‘application/json, text/plain, /‘,
‘User-Agent’: ‘axios/0.21.4’
>,
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: ‘XSRF-TOKEN’,
xsrfHeaderName: ‘X-XSRF-TOKEN’,
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
transitional: <
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
>,
URLSearchParams: < bid: ‘164450’, key: ‘AOJN5Dxs17fEAGUM’, uid: ‘1’, msg: ‘Test’ >,
data: undefined
>,
request: ClientRequest <
_events: [Object: null prototype] <
abort: [Function (anonymous)],
aborted: [Function (anonymous)],
connect: [Function (anonymous)],
error: [Function (anonymous)],
socket: [Function (anonymous)],
timeout: [Function (anonymous)],
prefinish: [Function: requestOnPrefinish]
>,
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
maxRequestsOnConnectionReached: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: »,
finished: true,
_headerSent: true,
_closed: false,
socket: Socket <
connecting: false,
_hadError: false,
_parent: null,
_host: ‘api.brainshop.ai’,
_readableState: [ReadableState],
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
_writableState: [WritableState],
allowHalfOpen: false,
_sockname: null,
_pendingData: null,
_pendingEncoding: »,
server: null,
_server: null,
parser: null,
_httpMessage: [Circular *1],
[Symbol(async_id_symbol)]: 152,
[Symbol(kHandle)]: [TCP],
[Symbol(kSetNoDelay)]: false,
[Symbol(lastWriteQueueSize)]: 0,
[Symbol(timeout)]: null,
[Symbol(kBuffer)]: null,
[Symbol(kBufferCb)]: null,
[Symbol(kBufferGen)]: null,
[Symbol(kCapture)]: false,
[Symbol(kBytesRead)]: 0,
[Symbol(kBytesWritten)]: 0,
[Symbol(RequestTimeout)]: undefined
>,
_header: ‘GET /get HTTP/1.1rn’ +
‘Accept: application/json, text/plain, /rn’ +
‘User-Agent: axios/0.21.4rn’ +
‘Host: api.brainshop.airn’ +
‘Connection: closern’ +
‘rn’,
_keepAliveTimeout: 0,
_onPendingData: [Function: nop],
agent: Agent <
_events: [Object: null prototype],
_eventsCount: 2,
_maxListeners: undefined,
defaultPort: 80,
protocol: ‘http:’,
options: [Object: null prototype],
requests: [Object: null prototype] <>,
sockets: [Object: null prototype],
freeSockets: [Object: null prototype] <>,
keepAliveMsecs: 1000,
keepAlive: false,
maxSockets: Infinity,
maxFreeSockets: 256,
scheduling: ‘lifo’,
maxTotalSockets: Infinity,
totalSocketCount: 1,
[Symbol(kCapture)]: false
>,
socketPath: undefined,
method: ‘GET’,
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: ‘/get’,
_ended: true,
res: IncomingMessage <
_readableState: [ReadableState],
_events: [Object: null prototype],
_eventsCount: 3,
_maxListeners: undefined,
socket: [Socket],
httpVersionMajor: 1,
httpVersionMinor: 1,
httpVersion: ‘1.1’,
complete: true,
rawHeaders: [Array],
rawTrailers: [],
aborted: false,
upgrade: false,
url: »,
method: null,
statusCode: 400,
statusMessage: ‘Bad Request’,
client: [Socket],
_consuming: false,
_dumped: false,
req: [Circular *1],
responseUrl: ‘http://api.brainshop.ai/get’,
redirects: [],
[Symbol(kCapture)]: false,
[Symbol(kHeaders)]: [Object],
[Symbol(kHeadersCount)]: 10,
[Symbol(kTrailers)]: null,
[Symbol(kTrailersCount)]: 0,
[Symbol(RequestTimeout)]: undefined
>,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: ‘api.brainshop.ai’,
protocol: ‘http:’,
_redirectable: Writable <
_writableState: [WritableState],
_events: [Object: null prototype],
_eventsCount: 2,
_maxListeners: undefined,
_options: [Object],
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: [Circular *1],
_currentUrl: ‘http://api.brainshop.ai/get’,
[Symbol(kCapture)]: false
>,
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype] <
accept: [Array],
‘user-agent’: [Array],
host: [Array]
>
>,
response: <
status: 400,
statusText: ‘Bad Request’,
headers: <
connection: ‘close’,
‘content-length’: ‘120’,
‘content-type’: ‘application/json; charset=utf-8’,
date: ‘Thu, 10 Mar 2022 03:12:32 GMT’,
server: ‘Cowboy’
>,
config: <
url: ‘http://api.brainshop.ai/get’,
method: ‘get’,
headers: [Object],
transformRequest: [Array],
transformResponse: [Array],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: ‘XSRF-TOKEN’,
xsrfHeaderName: ‘X-XSRF-TOKEN’,
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
transitional: [Object],
URLSearchParams: [Object],
data: undefined
>,
request: ClientRequest <
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
maxRequestsOnConnectionReached: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: »,
finished: true,
_headerSent: true,
_closed: false,
socket: [Socket],
_header: ‘GET /get HTTP/1.1rn’ +
‘Accept: application/json, text/plain, /rn’ +
‘User-Agent: axios/0.21.4rn’ +
‘Host: api.brainshop.airn’ +
‘Connection: closern’ +
‘rn’,
_keepAliveTimeout: 0,
_onPendingData: [Function: nop],
agent: [Agent],
socketPath: undefined,
method: ‘GET’,
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: ‘/get’,
_ended: true,
res: [IncomingMessage],
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: ‘api.brainshop.ai’,
protocol: ‘http:’,
_redirectable: [Writable],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
>,
data: < cnt: », status: [Object] >
>,
isAxiosError: true,
toJSON: [Function: toJSON]
>

Problem solved
Host recognises the chatSend Event as Spam!

Problem solved Host recognises the chatSend Event as Spam!

how did you solved it?
i am also getting the same issue

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Asked by: Dr. Sim Abernathy

Score: 4.4/5
(21 votes)

By default, the axios HTTP library throws an error anytime the destination server responds with a 4XX / 5XX error (for example, a 400 Bad Request ). Since axios raises an error, your workflow will stop at this step. See the axios docs for more information.

Does Axios throw errors?

Error Handling in Axios using `catch()`

Axios requests are promises, which means they have a then() function for promise chaining, and a catch() function for handling errors. … Axios’ catch() behaves exactly the same as the promise catch() function.

How do I get errors from Axios response?

In order to get the http status code returned from the server, you can add validateStatus: status => true to axios options: axios({ method: ‘POST’, url: ‘http://localhost:3001/users/login’, data: { username, password }, validateStatus: () => true }). then(res => { console. log(res.

How does Network Error handle Axios?

“handle network error in axios” Code Answer

axios. get(‘/api/xyz/abcd’)
. catch(function (error) {
if (error. response) {
// Request made and server responded.
console. log(error. response. data);
console. log(error. response. status);
console. log(error. response. headers);
} else if (error. request) {

How do I display errors in Axios?

“axios display error message from server” Code Answer’s

try {
await axios. get(‘/bad-call’)
} catch (error) {
const err = error as AxiosError.
if (err. response) {
console. log(err. response. status)
console. log(err. response. data)
}

26 related questions found

How do I fix an API error?

To fix the API call for those two situations, make sure that the credentials you are using have the access-level required by the endpoint, or that the access token has the correct permissions. A less common reason we might see this error is if we’re not explicit about the Accept header value.

How do you handle API errors?

The simplest way we handle errors is to respond with an appropriate status code. Here are some common response codes: 400 Bad Request – client sent an invalid request, such as lacking required request body or parameter. 401 Unauthorized – client failed to authenticate with the server.

What is network error?

A network error is the error condition that caused a network request to fail. Each network error has a type , which is a string. Each network error has a phase , which describes which phase the error occurred in: dns. the error occurred during DNS resolution.

What is Axios default timeout?

In Axios, the default timeout is set to 0. However, Axios allows you to set a custom timeout when required. One way to add a timeout is to pass it to the config object.

What is Net :: Err_name_not_resolved?

When you receive the “ERR_NAME_NOT_RESOLVED” error message, Chrome is saying that it could not find the IP address which matches the website domain name you entered. … You can encounter this error regardless of whether you are using Chrome on a desktop PC (Windows, macOS or Linux) or on a mobile device (Android or iOS).

How do you handle 400 error in react?

“catch 400 error with axios in react” Code Answer

axios. get(‘/api/xyz/abcd’)
. catch(function (error) {
if (error. response) {
// Request made and server responded.
console. log(error. response. data);
console. log(error. response. status);
console. log(error. response. headers);
} else if (error. request) {

How do you get 400 bad request?

How to Fix 400 Bad Request Error

Check the Submitted URL.
Clear Browser Cache.
Clear Browser Cookies.
File Upload Exceeds Server Limit.
Clear DNS Cache.
Deactivate Browser Extensions.

What’s a 400 error?

The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Does Axios throw error on non 200?

It’s not possible to retrieve response bodies for non 200 HTTP responses because Axios throws an exception for non 2xx codes. This does not complies to the browser Fetch API. Some APIs return data even if the response code is not 200 OK.

How do you mock Axios?

Let’s explain the first test in the above example:

Mock Axios: jest. mock(«axios»).
Create a sample response and make mocked axios instance return it: axios. …
Call the function you are testing (fetchUsers() in our example).
Confirm that the request was sent to the correct endpoint and that the correct result is returned.

How do I make Axios call asynchronous?

To use the async/await syntax, we need to wrap the axios. get() function call within an async function. We encase the method call with a try… catch block so that we can capture any errors, similar to the catch() method we used in the Promise version.

How do you handle Axios timeout?

If you’re making http requests using the axios library on a browser or in a node app, do make sure that you have a timeout set. The default timeout is set to 0 which indicates no timeout. With that default value, any remote end can keep us waiting for the requested resource for an indefinite period.

Does Axios return a promise?

Once you make a request, Axios returns a promise that will resolve to either a response object or an error object.

How do you fix network error?

Restart your device.

Restart your device. It might sound simple, but sometimes that’s all it takes to fix a bad connection.
If restarting doesn’t work, switch between Wi-Fi and mobile data: Open your Settings app «Wireless & networks» or «Connections». …
Try the troubleshooting steps below.

What causes a network error?

Network errors can be any of the following: DNS resolution errors, TCP connection timeout/error, or the server closing/resetting the connection with no response. … The cables & wires connecting your server to the Internet may or may not be able to handle the bits we’re trying to send through them.

How do I get rid of a network error?

If your app displays a network error message, try the following:

Turn Wi-Fi OFF in Settings > Wi-Fi > Off.
Turn Airplane Mode OFF in Settings > Airplane Mode > Off.
Turn Cellular Data ON in Settings App > Wireless & Networks (header) > More… > Mobile Networks > Data Enabled.

What does an API error mean?

If you get an ‘API Error’ message, it means something went wrong with the API request, maybe due to a missing parameter or module. API (Application Programming Interface) requests are messages that your Core web application uses to interact with our web servers.

How does REST API handle error response?

The REST API reports errors by returning an appropriate HTTP response code, for example 404 (Not Found), and a JSON response. Any HTTP response code that is not in the range 200 — 299 is considered an error.

How do I know if API is working?

Checking the API Response with your Browser

Open the Chrome developer console.
Search for ip.json.
Reload the Page.
Check the Firmographic Attribute Data.

Источник