The meow teaches you to remember the HTTP status code.

There are some difficulties in remembering HTTP status codes because the status code is a lot and difficult to remember. Girliemac, also known as Tomomi Imura, uses her ingenious idea to PS a series of HTTP status messages. After you've seen these pictures, you can definitely remember some HTTP status codes, because I just learned these status codes here.

These status codes and their most basic meanings are listed below

100 continue

Indicates that the server has received a request header and that the client should continue to send the request body.

101 Switching protocols

Indicates that the requester has requested the server to switch the protocol, and the server has accepted and will process it.

200 Normal

The standard answer for the successful HTTP request. The actual response content is determined by the method used by the request.

201 Created

The request has been accepted and the resource corresponding to the request has been created.

202 Acceptance

The request has been accepted, processing has not been completed, and it may be rejected.

204 No Content

The server did not return any entity content after the request was successfully processed.

207 Multi-weight status

Depending on the number of child requests, the message body contains different response codes.

300 multi-weight selection

Indicates that the requested resource can provide multiple options for the client to select

301 Permanent Removal

The request should be directed to the given URI (Uniform Resource Locator)

302 found

This is an example of conflicting industrial practices and standards. Some Web applications and frameworks use 302 status codes

303 See other information

The response to the current request can be obtained from another URI using the Get method

304 Not modified

Indicates that the resource has not been changed since the last request.

305 using Proxies

The requested resource must be accessed through the specified proxy, and most HTTP clients will not respond correctly to this status code, primarily for security reasons

307 Temporary redirection

In this case, the request will respond from a different URI, but future requests will still use the original URI

400 Error request

The request cannot be completed because of the wrong syntax

401 Not authorized

Status code returned when authorization is required, but authorization fails or is not authorized

402 Need to pay

This status code is reserved for possible future requirements. This code is usually not used, but its initial intent is to be used by some kind of electronic money.

403 Forbidden

The request is valid, but the server refuses to respond to it.

404 Not Found

The requested resource could not be found, but may be available in the future.

405 method does not allow

The request method used when requesting a resource cannot be supported by that resource.

406 No Access

The content that the requested resource can produce does not satisfy the type specified in the request header.

408 Request timed out

Server waits for Request timeout

409 conflicts

Request cannot be processed because a conflict exists in the request

410 deleted

The requested resource is no longer available, and subsequent is not available.

411 Data Length Required

The resource corresponding to the request needs to indicate the length, but the request does not contain a length.

413 Request Entity too large

Its request data entity is too large to exceed the server processing power.

414 Request URI too long

The URI is too long and the server cannot process

416 Request scope does not meet the requirements

The client requests some files, but the server does not provide this range value.

417 Hope Failure

The server does not meet the request header re-specified requirements.

418 I'm the teapot.

This status code is not implemented in the actual HTTP server

422 Non-processing request entity

The request is formatted correctly but cannot respond because of a semantic error.

423 Lock

Current resource is locked

424 Error Dependencies

This request failed because the previous request failed

425 Random Order Collection

Defined in the WebDAV advanced collections Draft

426 need to update

The client should switch to a different protocol

429 Too many requests

The user sent too many requests within the specified time.

431 Request Header too large

Because a single domain in the request is too large, or all of the fields add up too much.

444 No response

Used in Nginx records to indicate that the server has not returned information to the client and has closed the connection

450 blocked by Windows Parental controls

A status code extended by Microsoft

500 Server Internal Error

When no other more precise information can be given, a generic error message is given.

502 Error Gateway

An invalid response was received from the upstream server when the server acting as a gateway or agent tries to execute the request

503 Service Not available

The server is currently unavailable.

506 Variable Element negotiation

The requested transparent content negotiation causes a circular reference

507 Insufficient storage space

The server cannot store the content necessary to complete the request.

508 Loop Detected

The server found an infinite loop while processing the request

509 exceeding bandwidth limit

Although many servers use this protocol, they are not described in any RFC

599 Network Connection Timeout error

This status code is not described in any RFC, but Microsoft is using it.

Original link: http://blog.jobbole.com/88450/

The meow teaches you to remember the HTTP status code.