{"slug":"fetch-promise-is-resolved-even-on-4xx-and-5xx-response-codes","frontmatter":{"content":"\nI have been assuming all this time that fetch promise must be rejected on 4xx and 5xx response codes. Because this has been the behaviour with `jQuery.ajax` and `axios`. But `fetch` doesn't follow that. A fetch promise is only considered rejected when the client is not able to establish a connection to the server e.g. Host down, No internet connection, Server refused the connection etc\n\nMore details on this [StackOverflow Post](https://stackoverflow.com/a/39297738/1109657)","data":{"category":"TIL","creationTs":1631017260000,"date":"September 7, 2021 2:21 PM","lastModified":"September 9, 2021 3:10 PM","lastModifiedTs":1631193000000,"published":"Yes","title":"fetch promise is resolved even on 4xx and 5xx response codes"},"isEmpty":false,"excerpt":"","category":["TIL"],"creationTs":1631017260000,"date":"September 7, 2021","lastModified":"September 9, 2021 3:10 PM","lastModifiedTs":1631193000000,"published":"Yes","title":"fetch promise is resolved even on 4xx and 5xx response codes","updated":"September 9, 2021"},"content":"

I have been assuming all this time that fetch promise must be rejected on 4xx and 5xx response codes. Because this has been the behaviour with jQuery.ajax and axios. But fetch doesn't follow that. A fetch promise is only considered rejected when the client is not able to establish a connection to the server e.g. Host down, No internet connection, Server refused the connection etc