how to catch 400 bad request error in HTTP response in angular2

Question

I try to catch error 400 bad request like this:

catch((error: any) => {
    if (error.status === 500) {
        return Observable.throw(new Error(error.status));
    }
    else if (error.status === 400) {
        console.log( 'error' );
        return Observable.throw(new Error(error.status));
    }

but it still appears like this in the console:

Do you have any idea how to fix this problem or remove this message on console?

Thanks a lot.

Can you post the message? Some people have imgur blocked by work. — joh04667, Jun 14 '17 at 18:52
I don't think you can prevent the console from logging the error on the client side. — Brandon Taylor, Jun 14 '17 at 20:06

score -2 · Accepted Answer · answered Jun 14 '17 at 20:52

-2

This is the browser's standard behavior and cannot be influenced by you or Angular.

If you get those messages a lot and it clutters your console whilst developing, you can filter the console. This is how you would do it in Chrome:

see also https://stackoverflow.com/a/14427545/4694994

answered Jun 14 '17 at 20:52

Kim Kern

43,715
16
163
170

do you thinks this make a clean.console by js can be a solution?? or you think this is not a problem or error of the sistem???? – Sergio Agosto Enriquez Jun 14 '17 at 21:14
I'm not sure if I understood your first question correctly. Can you clarify? – Kim Kern Jun 14 '17 at 21:24
In general, it's perfectly fine to catch errors and handle them on your client. That said, your server should only respond with 400, if the request was invalid. Don't use it for valid requests, that have a non-normal response. For example for 'empty content', you should use the success code 204. – Kim Kern Jun 14 '17 at 21:33
You did solve my question thanks a lot – Sergio Agosto Enriquez Jun 14 '17 at 22:19
this happens with 403 and 409 as well. not sure how to handle this – Rishabh Agrawal Jun 10 '20 at 11:32

how to catch 400 bad request error in HTTP response in angular2

1 Answers1