Author: Web developer www.sohu.com/a/190263277…

HTTP Status Code is a 3-digit Code used to indicate the HTTP response Status of a web server.

We can judge the server status by viewing the HTTP status code, common 404, 502, etc.; But what about the other less common status codes? Here are two interesting pictures that will make you understand in an instant.

HTTP status code (Figure 1)

  • 301 — Permanent move. The requested resource has been permanently moved;

  • 302 – The requested resource now temporarily responds to the request from a different URI;

  • 305 — Use a proxy. The requested resource must be accessed through a specified proxy;

  • 307 — Temporary jump. The requested resource temporarily responds to the request from a different URL;

  • 400 – Error request;

  • 402 — Payment is required. The status code is reserved for possible future demand for some digital currency or micropayments;

  • 403 — Access is disabled. The server understands the request, but refuses to execute it;

  • 404 – Object not found. The request failed. The resource does not exist.

  • 406 — Unacceptable. The content characteristics of the requested resource do not meet the conditions in the request header, so the response entity cannot be generated;

*

HTTP status code (Figure 2)

  • 408 – Request timed out;

  • 409 – conflicts. The request could not be completed because of a conflict with the current state of the requested resource.

  • 410 — Lost. The requested resource is no longer available on the server and does not have any known forwarding address;

  • 413 — Response entity is too large. The server refused to process the current request. The request exceeded the maximum value that the server can process and allow.

  • 417 — Expect failure. The expected content specified in request header Expect cannot be satisfied by the server;

  • 418 — I’m a teapot. Hypertext coffee can control protocol, but not implemented by actual HTTP servers;

  • 420 — Method failure.

  • 422 — Unprocessable entity. The request was well-formed, but could not be responded to due to semantic errors;

  • 500 – Server internal error. The server encountered an unexpected condition that prevented it from completing processing the request;

Read more on my blog:

1.Java JVM, Collections, Multithreading, new features series tutorials

2.Spring MVC, Spring Boot, Spring Cloud series tutorials

3.Maven, Git, Eclipse, Intellij IDEA series tools tutorial

4.Java, backend, architecture, Alibaba and other big factory latest interview questions

Life is good. See you tomorrow