Learn about HTTP codes [Part-1]

[msrasel]

By browsing the Internet, we can sometimes see 404 Page not found or 503 Service Unavailable error. Also read more different HTTP success or error codes. But many people do not know about these codes containing different numbers. Today, in my tunes, I will try to give some idea about those codes.

1xx Informational

Codes starting with 1 mean that the request has been received on the server, and the request is being processed.

(Just like the status line and the optional headers, this type of status code indicates the response to different conditions, since the 1xx status code for HTTP / 1.0 is not used, so the server must send 1xx Response to an HTTP / 1.0 client without any experimental conditions. No.)

100 continue

This means that the requested request header is received on the server, and the client can send the requested request. If a request fails on the server due to an incorrect header, it is futile to send a large request request body to the server. In order to know whether the request will be accepted based on the header only, a client must send the Expect: 100-release code as the initial request header and before starting the job, it must be checked that the 100-release status Code received by server. (If the server responds as long as 417 Expectation Failed code should not be done.)

101 Switching Protocols

By this code, the requesting server is requesting the server to switch protocols and the server responded.

102 Processing (WebDAV) (RFC 2518)

As such a WebDAV request may contain many sub-requests, it may take a long time to perform such a request. Such code means that the request was received by the server and the server is processing the request but no response is available till now. As a result, the client understands that the work is going on and its request is not lost.

To be continued.....

Comments

[krguidedog]

Woff, woff!

Hello @msrasel, Nice to meet you!

I'm a guide dog living in KR community. I can see that you want to contribute to KR community and communicate with other Korean Steemians. I really appreciate it and I'd be more than happy to help.

KR tag is used mainly by Koreans, but we give warm welcome to anyone who wish to use it. I'm here to give you some advice so that your post can be viewed by many more Koreans. I'm a guide dog after all and that's what I do!

Tips:

• If you're not comfortable to write in Korean, I highly recommend you write your post in English rather than using Google Translate.
  Unfortunately, Google Translate is terrible at translating English into Korean. You may think you wrote in perfect Korean, but what KR Steemians read is gibberish. Sorry, even Koreans can't understand your post written in Google-Translated Korean.
• So, here's what might happen afterward. Your Google-Translated post might be mistaken as a spam so that whales could downvote your post. Yikes! I hope that wouldn't happen to you.
• If your post is not relevant to Korea, not even vaguely, but you still use KR tag, Whales could think it as a spam and downvote your post. Double yikes!
• If your post is somebody else's work(that is, plagiarism), then you'll definitely get downvotes.
• If you keep abusing tags, you may be considered as a spammer. It may result to put you into the blacklist. Oops!

I sincerely hope that you enjoy Steemit without getting downvotes. Because Steemit is a wonderful place. See? Korean Steemians are kind enough to raise a guide dog(that's me) to help you!

Woff, woff! 🐶

[ayogom]

kr-guide!

[soohyeongk]

kr-guide!