List Of HTTP Status Codes
source link: https://dev.to/capscode/list-of-http-status-codes-4ph
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
List Of HTTP Status Codes
Hello Devs,
In this blog I am going to discuss about the https status code in an API calls.
I know, you all must have worked on many API's till date and also checked the Network tab in browser's Developers tool to check whether the HTTP request is success or its failed. But have you ever seen something called status code in the network tab, which contain some random numbers like 200, 404, 501 etc.
In this blog I am going to discuss about these numbers, what these numbers are and what these numbers denotes.
So without wasting time, lets get deep dive into the tutorial.
What is status code ?
HTTP response status codes indicates that whether the request made by you or your browser has been successfully completed or not.
Depending on the response status you will get the different status code.
Status codes are categorized in the following 5 groups.
- Informational responses (status code between 100–199)
- Successful responses (status code between 200–299)
- Redirects (status code between 300–399)
- Client errors (status code between 400–499)
- Server errors (status code between 500–599)
Lets see some of the general status code in each category.
1. Informational responses (status code between 100–199)
100 Continue, if status code is 100, it indicates that the response is OK and you can continue to make other request.
101 Switching Protocols
102 Processing
2. Successful responses (status code between 200–299)
200 OK
201 Created
202 Accepted
203 Non-authoritative Information
204 No Content
205 Reset Content
206 Partial Content
207 Multi-Status
208 Already Reported
226 IM Used
3.Redirects (status code between 300–399)
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
307 Temporary Redirect
308 Permanent Redirect
4. Client errors (status code between 400–499)
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Payload Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
418 I'm a teapot
421 Misdirected Request
422 Unprocessable Entity
423 Locked
424 Failed Dependency
426 Upgrade Required
428 Precondition Required
429 Too Many Requests
431 Request Header Fields Too Large
444 Connection Closed Without Response
451 Unavailable For Legal Reasons
499 Client Closed Request
5. Server errors (status code between 500–599)
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates
507 Insufficient Storage
508 Loop Detected
510 Not Extended
511 Network Authentication Required
599 Network Connect Timeout Error
Thank you for reading this far. These HTTP status code are the most commonly used status codes while working with the API calls. If you want to learn more about the other staus codes, please visit MDN Doc
If you find this article useful, like and share this article. Someone could find it useful too. If you find anything technically inaccurate please feel free to reach out to us.
Hope its a nice and informative read for you.
VISIT https://www.capscode.in/blog TO LEARN MORE...
IF MY ARTICLE HELPED YOU
See you in my next Blog article, Take care!!
source/ credit: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
Thanks,
CapsCode
Recommend
-
42
Rust 1.26 introduced the ability to return a Result from the main method, which was a great ergonomics improvement especially for small CLI applications. If your application returns an...
-
13
Web Development...
-
11
A Non-Jargon Guide to HTTP Status CodesMichelle OfiweMar 22, 202110 min readHTTP, or HyperText Transfer Protocol, is the backbone of the Wo...
-
9
Are there standard output status codes in Linux? advertisements A process is considered to have completed correctly in Linux if its exit statu...
-
7
About this Episode Catalin Ciubotaru joins the adventure to discuss how to get Angular Universal to send server side HTTP codes to the browser from the back-end when Angular is geared toward the front-end and does...
-
5
The list of HTTP status codes and their explanation Author: Hamster, ...
-
10
Everything You Need to Know About HTTP Response Status CodesHTTP response codes are often ignored, but they are a really important mechanism to standardize responses from remote servers. When a program (or user) issues a r...
-
9
10 Error Status Codes When Building APIs for the First Time and How To Fix Them ...
-
5
hssp for Http StatuS where the two capitals S replace the two ts of http. This CLI is here to help you find/remember the meaning of an http status code. Historically speaking, this tool was written after struggling with...
-
10
You're Not Using HTTP Status Codes Right HTTP status codes are like short messages returned from a server whenever we request or interact with a resource on the serve...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK