2 ms·

I think you answered your own question! What if the processing times out and you need to send a 4xx code?

• xg15 2y ago
  Good point! I do think that most uses of the status code are either redundant (e.g. in API responses there is usually a second, much more detailed error description in the body), doesn't fit the data model (404 can mean everything from "you mistyped the service name" to "this entity does not exist", there is a retrofuturistic "payment required" code that has nothing to do with real ecommerce) or without consequence (if it's just shown in the browser) I still don't want to argue for sending the wrong status codes like in the bad old times - it absolutely can be a problem for intermediaries - but I wouldn't have thought it to be enough of a problem to warrant its own additional protocol feature. But I absolutely agree that, now that we have it, the 103 code is far better than any kind of hack.