# HTTP 555: User-Defined Resource Error

DevFeed: [HTTP 555: User-Defined Resource Error](<https://devfeed.tech/articles/http-555-user-defined-resource-error-19086.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/new-http-status-code-555/>)

Author: HTTP Toolkit; Tim Perry

Published: 2020-03-27T13:30:00Z

Content type: article

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [errors](<https://devfeed.tech/tags/errors.md>), [http](<https://devfeed.tech/tags/http.md>), [http-server](<https://devfeed.tech/tags/http-server.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [standards](<https://devfeed.tech/tags/standards.md>)

## AI overview

The article examines Oracle's proposed HTTP status code 555 for server-side errors caused by user-supplied resources in serverless systems. It explains HTTP status-code categories and emphasizes that the proposal is not standardized and should not be used in production.

## Source excerpt

Does the rise of serverless mean we need a new HTTP status code? The team at Oracle think so. They've submitted a draft specification to the HTTP Working Group, defining a new HTTP status code (initially suggesting 555) to be used for server-side errors caused by user-supplied resources. [Note: I'm going to use 555 to refer to the new proposed code everywhere here, but this is not standardized, even if it is standardized in future it will probably use a different code, and you 100% should not start building anything that uses this code for real anywhere. Nobody needs another 418 I'm A Teapot battle.] Anyway, let's talk about what this means, and whether it's a good idea. Status codes: a refresher First let's recap the background. Status codes are 3 digit codes, included in every response from an HTTP server, which summarize the result of a request. There's common examples you'll have heard of like 404 (the resource you requested could not be found) or 200 (your request was successful, and this response represents the result). There's then a long list of less common examples, like 302 (the resource you requested is a temporarily stored elsewhere, you should go there instead), 410 (the resource you requested was here, but now it's gone, and there's no new address available), or 100 (yes, please continue sending the rest of the request you're already sending). And many more. They're categorized into a few classes: 1XX: Information These are provisional responses, which typically don't fit into the simple HTTP request/response flow, and describe unusual behaviors like interim responses or switching the connection to a different protocol. 2XX: Success The request you asked for was successful in some way. Perhaps you're getting the resource you asked for (200), the server has accepted and started asynchronously processing your operation (202), or your request was successful but the server doesn't have any data about it for you (204). 3XX: Redirection Your request is valid