Enum HttpCode

pub enum HttpCode {
    Continue,
    SwitchingProtocols,
    Processing,
    EarlyHints,
    Ok,
    Created,
    Accepted,
    NonAuthoritativeInformation,
    NoContent,
    ResetContent,
    PartialContent,
    MultiStatus,
    AlreadyReported,
    ImUsed,
    MultipleChoices,
    MovedPermanently,
    Found,
    SeeOther,
    NotModified,
    TemporaryRedirect,
    PermanentRedirect,
    BadRequest,
    Unauthorized,
    PaymentRequired,
    Forbidden,
    NotFound,
    MethodNotAllowed,
    NotAcceptable,
    ProxyAuthentificationRequired,
    RequestTimeout,
    Conflict,
    Gone,
    LengthRequired,
    PreconditionFailed,
    PayloadTooLarge,
    UriTooLong,
    UnsupportedMediaType,
    RangeNotSatisfiable,
    ExpectationFailed,
    ImATeapot,
    MisdirectedRequest,
    UnprocessableContent,
    Locked,
    FailedDependency,
    TooEarly,
    UpgradeRequired,
    PreconditionRequired,
    TooManyRequests,
    RequestHeaderFieldsTooLarge,
    UnavailableForLegalReasons,
    InternalServerError,
    NotImplemented,
    BadGateway,
    ServiceUnavailable,
    GatewayTimeout,
    HttpVersionNotSupported,
    VariantAlsoNegotiates,
    InsufficientStorage,
    LoopDetected,
    NotExtended,
    NetworkAuthetificationRequired,
    None,
    Unknown(u32),
}

The HTTP codes with all their descriptions. Thanks to MDN for the documentation

Variants

Continue

Code 100

This interim response indicates that the client should continue the request or ignore the response if the request is already finished.

SwitchingProtocols

Code 101

This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.

Processing

Code 102 (WebDAV)

This code indicates that the server has received and is processing the request, but no response is available yet.

EarlyHints

Code 103

This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response or preconnect to an origin from which the page will need resources.

Ok

Code 200

The request succeeded. The result meaning of “success” depends on the HTTP method:

• GET: The resource has been fetched and transmitted in the message body.
• HEAD: The representation headers are included in the response without any message body.
• PUT or POST: The resource describing the result of the action is transmitted in the message body.
• TRACE: The message body contains the request message as received by the server.

Created

Code 201

The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.

Accepted

Code 202

The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

NonAuthoritativeInformation

Code 203

This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the 200 OK response is preferred to this status.

NoContent

Code 204

There is no content to send for this request, but the headers may be useful. The user agent may update its cached headers for this resource with the new ones.

ResetContent

Code 205

Tells the user agent to reset the document which sent this request.

PartialContent

Code 206

This response code is used when the Range header is sent from the client to request only part of a resource.

MultiStatus

Code 207 (WebDAV)

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

AlreadyReported

Code 208 (WebDAV)

Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.

ImUsed

Code 226 (HTTP Delta encoding)

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

MultipleChoices

Code 300

The request has more than one possible response. The user agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)

MovedPermanently

Code 301

The URL of the requested resource has been changed permanently. The new URL is given in the response.

Found

Code 302

This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.

SeeOther

Code 303

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

NotModified

Code 304

This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.

TemporaryRedirect

Code 307

The server sends this response to direct the client to get the requested resource at another URI with the same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

PermanentRedirect

Code 308

This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

BadRequest

Code 400

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Unauthorized

Code 401

Although the HTTP standard specifies “unauthorized”, semantically this response means “unauthenticated”. That is, the client must authenticate itself to get the requested response.

PaymentRequired

Code 402 (Experimental)

This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.

Forbidden

Code 403

The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client’s identity is known to the server.

NotFound

Code 404

The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.

MethodNotAllowed

Code 405

The request method is known by the server but is not supported by the target resource. For example, an API may not allow calling DELETE to remove a resource.

NotAcceptable

Code 406

This response is sent when the web server, after performing server-driven content negotiation, doesn’t find any content that conforms to the criteria given by the user agent.

ProxyAuthentificationRequired

Code 407

This is similar to 401 Unauthorized but authentication is needed to be done by a proxy.

RequestTimeout

Code 408

This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.

Conflict

Code 409

This response is sent when a request conflicts with the current state of the server.

Gone

Code 410

This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for “limited-time, promotional services”. APIs should not feel compelled to indicate resources that have been deleted with this status code.

LengthRequired

Code 411

Server rejected the request because the Content-Length header field is not defined and the server requires it.

PreconditionFailed

Code 412

The client has indicated preconditions in its headers which the server does not meet.

PayloadTooLarge

Code 413

Request entity is larger than limits defined by server. The server might close the connection or return an Retry-After header field.

UriTooLong

Code 414

The URI requested by the client is longer than the server is willing to interpret.

UnsupportedMediaType

Code 415

The media format of the requested data is not supported by the server, so the server is rejecting the request.

RangeNotSatisfiable

Code 416

The range specified by the Range header field in the request cannot be fulfilled. It’s possible that the range is outside the size of the target URI’s data.

ExpectationFailed

Code 417

This response code means the expectation indicated by the Expect request header field cannot be met by the server.

ImATeapot

Code 418

The server refuses the attempt to brew coffee with a teapot.

MisdirectedRequest

Code 421

The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.

UnprocessableContent

Code 422 (WebDAV)

The request was well-formed but was unable to be followed due to semantic errors.

Locked

Code 423 (WebDAV)

The resource that is being accessed is locked.

FailedDependency

Code 424 (WebDAV)

The request failed due to failure of a previous request.

TooEarly

Code 425 (Experimental)

Indicates that the server is unwilling to risk processing a request that might be replayed.

UpgradeRequired

Code 426

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).

PreconditionRequired

Code 428

The origin server requires the request to be conditional. This response is intended to prevent the ‘lost update’ problem, where a client GETs a resource’s state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.

TooManyRequests

Code 429

The user has sent too many requests in a given amount of time (“rate limiting”).

RequestHeaderFieldsTooLarge

Code 431

The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.

UnavailableForLegalReasons

Code 451

The user agent requested a resource that cannot legally be provided, such as a web page censored by a government.

InternalServerError

Code 500

The server has encountered a situation it does not know how to handle.

NotImplemented

Code 501

The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.

BadGateway

Code 502

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

ServiceUnavailable

Code 503

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.

GatewayTimeout

Code 504

This error response is given when the server is acting as a gateway and cannot get a response in time.

HttpVersionNotSupported

Code 505

The HTTP version used in the request is not supported by the server.

VariantAlsoNegotiates

Code 506

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.

InsufficientStorage

Code 507 (WebDAV)

The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.

LoopDetected

Code 508 (WebDAV)

The server detected an infinite loop while processing the request.

NotExtended

Code 510

Further extensions to the request are required for the server to fulfill it.

NetworkAuthetificationRequired

Code 511

Indicates that the client needs to authenticate to gain network access.

None

No code were given

Unknown(u32)

A code was given but is unknown to the library

Implementations

impl HttpCode

pub fn to_class(self) -> HttpCodeClass

Returns the class associated to the code

pub fn is_informational(&self) -> bool

Returns true if the code is 1xx

pub fn is_successful(&self) -> bool

Returns true if the code is 2xx

pub fn is_redirection(&self) -> bool

Returns true if the code is 3xx

pub fn is_client_error(&self) -> bool

Returns true if the code is 4xx

pub fn is_server_error(&self) -> bool

Returns true if the code is 5xx

pub fn is_unknown(&self) -> bool

Returns true if the code is unknown

pub fn is_none(&self) -> bool

Returns true if there is no code

Trait Implementations

impl Clone for HttpCode

fn clone(&self) -> HttpCode

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Default for HttpCode

fn default() -> Self

Returns the “default value” for a type.

impl From<HttpCode> for HttpCodeClass

fn from(value: HttpCode) -> Self

Converts to this type from the input type.

impl From<HttpCode> for Option<u32>

fn from(value: HttpCode) -> Self

Converts to this type from the input type.

impl From<HttpCode> for u32

fn from(value: HttpCode) -> Self

Converts to this type from the input type.

impl From<Option<i128>> for HttpCode

fn from(value: Option<i128>) -> Self

Converts to this type from the input type.

impl From<Option<i16>> for HttpCode

fn from(value: Option<i16>) -> Self

Converts to this type from the input type.

impl From<Option<i32>> for HttpCode

fn from(value: Option<i32>) -> Self

Converts to this type from the input type.

impl From<Option<i64>> for HttpCode

fn from(value: Option<i64>) -> Self

Converts to this type from the input type.

impl From<Option<isize>> for HttpCode

fn from(value: Option<isize>) -> Self

Converts to this type from the input type.

impl From<Option<u128>> for HttpCode

fn from(value: Option<u128>) -> Self

Converts to this type from the input type.

impl From<Option<u16>> for HttpCode

fn from(value: Option<u16>) -> Self

Converts to this type from the input type.

impl From<Option<u32>> for HttpCode

fn from(value: Option<u32>) -> Self

Converts to this type from the input type.

impl From<Option<u64>> for HttpCode

fn from(value: Option<u64>) -> Self

Converts to this type from the input type.

impl From<Option<usize>> for HttpCode

fn from(value: Option<usize>) -> Self

Converts to this type from the input type.

impl From<i128> for HttpCode

fn from(value: i128) -> Self

Converts to this type from the input type.

impl From<i16> for HttpCode

fn from(value: i16) -> Self

Converts to this type from the input type.

impl From<i32> for HttpCode

fn from(value: i32) -> Self

Converts to this type from the input type.

impl From<i64> for HttpCode

fn from(value: i64) -> Self

Converts to this type from the input type.

impl From<isize> for HttpCode

fn from(value: isize) -> Self

Converts to this type from the input type.

impl From<u128> for HttpCode

fn from(value: u128) -> Self

Converts to this type from the input type.

impl From<u16> for HttpCode

fn from(value: u16) -> Self

Converts to this type from the input type.

impl From<u32> for HttpCode

fn from(value: u32) -> Self

Converts to this type from the input type.

impl From<u64> for HttpCode

fn from(value: u64) -> Self

Converts to this type from the input type.

impl From<usize> for HttpCode

fn from(value: usize) -> Self

Converts to this type from the input type.

impl Copy for HttpCode