Home/ Questions/Q 7191797
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T19:48:19+00:00

Basically it boils down to, is there any case where it would be bad

  • 0

Basically it boils down to, is there any case where it would be bad for me to call the success callback function on status codes under 400?

In looking at the list of status codes for HTTP, I don’t think there would be but I want to make sure. I don’t think I’ll be getting 1XX level codes as they look like most of them return before the full request is processed and readyState === 4 (I don’t care about IE 7’s 122). And I want to still return success on a 302 and 304 status codes. So is status < 400 an acceptable way to catch all of this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Building on @sarnold’s concerns, it looks like the XMLHttpRequest specifications say the following:

    If the response is an HTTP redirect (status code 301, 302, 303 or
    307), then it MUST be transparently followed (unless it violates
    security or infinite loop precautions). Any other error (including a
    401) MUST cause the object to use that error page as the response.

    Which seems to indicate to me that either 2XX or 3XX responses are valid. So, in short, my findings indicate status < 400 is an appropriate status response check.

    • 0