List of Internet/Web error codes with meanings

By -
Error Page Not Found

Many a times, while browsing the Internet, you might come across various error codes. While some of the error code are self explanatory, some leaves the users to ponder around. Here, I'm listing all the error codes with their meanings. Bookmark this page as this might come handy to you someday!

1XX codes (Information)

This group of codes evaluates a provisional response, inclusing only the Status-Line, and optional headers.

100 - Continue
101 - Switching Protocols
102 - Processing

2XX codes (Success)

This group of codes evaluate that the action requested by the user has been received, understood, accepted, and or processed successfully.

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

3XX codes (Redirection)

This group of codes evaluates that the user must take additional action to complete the sent request.

300 - Multiple Choices
301 - Moved Permanently
302 - Found
305 - Use Proxy
306 - Switch Proxy
307 - Temporary Redirect
308 - Permanent Redirect

4XX codes (Client Error)

This group of code is made for situations where the client is seem to have erred.

400 - Bad Request
401 - Unauthorized (RFC 7235)
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 - URI Too Long
415 - Unsupported Media Type
416 - 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
451 - Unavailable For Legal Reasons

5XX codes (Server Error)

This group of code evaluates that the server has failed to respond to a valid request.

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

Comments

Post a Comment

Note: Your comment won't be published if it includes abusive words, disrespect or links to external websites.

Popular posts from this blog

[FIXED] Code::Blocks error: 'cout' was not declared in this scope

By -
Image
Code::Blocks error: 'cout' was not declared in this scope T his is one of the most common errors you get if you download or create a C++ project on your Code::Blocks IDE and try to compile it using GNU GCC compiler (the default compiler in Code::Blocks). This problem is common with people who've recently moved to Code::Blocks from an older IDE. This happens because Code::Blocks fails to see 'cout' keyword as a local scope unless its defined as a standard directory function. Luckily, there are two simple ways to fix this error: Method 1 Use this statement before your main function: using namespace std; So that your code looks something like: #include <iostream> using namespace std; int main() {     cout << "Hello world!";     return 0; } Method 2 Instead of using cout , try using std::cout so that the code looks something like: #include <iostream> int main() {     std::cout << "Hello world!"...
Read more

How to know if someone has read your message with Read Receipt disabled on WhatsApp?

By -
Image
  When a message gets delivered to the receiver, you see a double tick. And when they read the message, the double tick becomes blue. However, if the receiver has disabled/turned off 'Read Receipt' option on their WhatsApp settings, you can only see a double tick after sending a message whether they've read it or not. Thus, making it impossible to guess whether they've seen the message or not. Let's make it possible. Today, I'll show you a small trick with the help of which, you'll be able to know whether or not they have read your message. It works 95% of the times. Steps: First of all, type and send your desired message. Here, I'm using a Windows Phone to illustrate it, it works the same way on Android and iOS devices. Record a 3-4 seconds audio and send it after sending the messages. Next, when they see your messages, there's a high chance that they'll play your recorded audio. As soon as your recording is played, the audio mess...
Read more