WEBVTT 00:00.110 --> 00:03.740 Hey, everyone, and welcome back to the Knowledge Portal Video series. 00:03.770 --> 00:10.370 Now, we had a high level overview about various type of request methods which a client can send to 00:10.370 --> 00:11.390 a web server. 00:11.480 --> 00:19.490 Now, in response to that request, methods, a web server might send a certain Http status code like 00:19.490 --> 00:23.200 success or not found or some kind of error as well. 00:23.210 --> 00:30.740 So these are called as the Http status codes, and we'll have a high level overview about the Http status 00:30.740 --> 00:31.610 codes as well. 00:32.240 --> 00:40.580 Now, as we already discussed, a client sends a request to the web server asking for get documented 00:40.580 --> 00:44.400 or MP4, and the web server sends a response back. 00:44.420 --> 00:55.160 Now, depending upon the response which a web server formulates for this specific request as a Http 00:55.550 --> 00:58.160 response code is basically generated. 00:58.160 --> 01:02.910 So this this specific code you see 200. 01:02.910 --> 01:05.040 Okay is called as the status code. 01:05.070 --> 01:06.810 Now, it might happen. 01:06.810 --> 01:14.340 Let's say, for example, a client send a request, get documentary dot mp4 and there is no such file 01:14.370 --> 01:18.310 called as documentary dot mp4 in the web server. 01:18.330 --> 01:22.740 Now, in that case, web server cannot send a 200, okay? 01:22.740 --> 01:25.860 Because there is no such file itself. 01:25.860 --> 01:27.840 So that is one possibility. 01:28.860 --> 01:37.290 Second possibility is present like the documentary dot MP4 is present, but the client does not have 01:37.290 --> 01:40.830 a permission to view this file or fetch this file. 01:40.830 --> 01:43.390 So that is the second possibility. 01:43.410 --> 01:48.150 So there can be lot of such possibilities which might be available. 01:48.210 --> 01:54.020 Or third possibility is like client sends a delete call or delete request method on documentary dot 01:54.030 --> 01:57.780 mp4 and the web server might not accept the request. 01:57.780 --> 02:06.300 So depending upon the situation, the response of the web server might be different and corresponding 02:06.330 --> 02:07.650 to each response. 02:07.650 --> 02:10.860 The status code which will be sent will be different. 02:10.890 --> 02:12.090 200 okay. 02:12.090 --> 02:14.090 Basically means successfully processed. 02:14.100 --> 02:17.820 You can have a 404 or 400 and 3 or 401. 02:17.820 --> 02:18.570 ET cetera. 02:18.570 --> 02:19.200 ET cetera. 02:19.200 --> 02:25.020 So this specific aspect is called as the status code. 02:25.020 --> 02:31.560 And you need to remember high level overview about various status codes which are available in the Http 02:31.560 --> 02:32.310 protocol. 02:32.880 --> 02:38.490 Now, there are various response status codes which are available. 02:38.850 --> 02:40.980 One is the 100 series. 02:40.980 --> 02:45.150 So these are the 100 series which are called as the Informational status code. 02:45.180 --> 02:50.400 You have the 200 series which are generally indicated as a success status. 02:50.400 --> 02:54.000 Code 300 series are called as the redirection status. 02:54.000 --> 03:04.620 Code 400 series are something related to some error from the client side and 500 series relates to some 03:04.620 --> 03:06.030 error from the server side. 03:06.270 --> 03:08.580 So let's have a high level overview. 03:08.590 --> 03:15.720 So 200 status codes indicates that the action is received and. 03:16.910 --> 03:20.350 Is successfully understood, accepted and processed. 03:20.380 --> 03:27.670 So whatever action which has been received by the server from the client is successfully understood, 03:27.670 --> 03:29.780 accepted and processed. 03:29.800 --> 03:31.750 So this is what I call as the. 03:33.220 --> 03:34.690 200 status code. 03:34.780 --> 03:37.210 Now, some of the example is 200. 03:37.210 --> 03:37.570 Okay. 03:37.600 --> 03:39.250 206 partial content. 03:39.250 --> 03:43.570 So these are the very famous response status code. 03:43.600 --> 03:48.660 Now, there are a lot of others as well, but we will not be going too much in depth right now. 03:48.670 --> 03:50.320 Whenever a need arises. 03:50.320 --> 03:54.520 In a practical session, we'll be discussing more about 200 series status code. 03:55.240 --> 04:02.130 Now, 300 status codes indicates that client must take additional steps to complete the request. 04:02.140 --> 04:11.590 So whatever request that the client has sent, that request is not good enough to have a successful 04:11.590 --> 04:12.040 response. 04:12.040 --> 04:19.660 So there are some additional steps which a client must take, and these additional steps can be informed 04:19.660 --> 04:25.120 by the web server so web server can tell a client that you should be doing these additional steps to 04:25.120 --> 04:26.680 complete a request. 04:26.710 --> 04:33.770 Now, one of the famous 300 series status codes are generally part of the URL redirection, and some 04:33.770 --> 04:40.640 of them is 301, which basically indicates that the page is moved permanently and 304, which is called 04:40.640 --> 04:44.060 as not modified, which is generally used in the caching mechanisms. 04:44.240 --> 04:51.710 We'll be discussing in detail about these status codes in the relevant practical session that will be 04:51.710 --> 05:00.020 having 400 series status codes indicates that a client seemed to have sent some requests, which is 05:00.020 --> 05:03.250 an not an idle one or an error sum. 05:03.380 --> 05:09.350 So one of the very famous that you might have seen is 404 page not found, which looks something similar 05:09.350 --> 05:09.880 to this. 05:09.890 --> 05:16.130 You also have a 403 forbidden, which basically means client does not really have a permission to view 05:16.130 --> 05:16.920 this page. 05:16.940 --> 05:24.200 Now in case if there is some kind of a Http authentication like basic authentication or digest authentication, 05:24.200 --> 05:26.000 you have a 401. 05:26.120 --> 05:33.770 Which basically will ask client for a username and password before the contents are being viewed by 05:33.770 --> 05:34.520 the client. 05:34.940 --> 05:40.670 Last but not the least, you have the 500 series status code, which basically indicates that there 05:40.670 --> 05:44.870 is some issue on the server side and it has failed to fulfill the request. 05:44.900 --> 05:51.710 Now there can be a possibility that there are some issues on the web server side also, and those issues 05:51.710 --> 05:54.540 are indicated by the 500 series status code. 05:54.540 --> 05:57.560 So one of the famous ones is internal server error. 05:57.570 --> 05:59.680 I'm sure you are aware about that. 05:59.690 --> 06:02.660 You might have seen internal server error a lot of time. 06:02.660 --> 06:04.460 So that is one of the example. 06:04.460 --> 06:13.280 You have 504 gateway time out like client might be expecting or there might be a timeout of 20s in which 06:13.280 --> 06:15.890 the server is not able to respond. 06:15.900 --> 06:18.260 So you have a 504 gateway timeout. 06:18.290 --> 06:21.290 You also have 503 service unavailable. 06:21.770 --> 06:27.380 So these are a high level overview about the Http status codes. 06:27.380 --> 06:30.520 I hope you understood the basic about status code. 06:30.530 --> 06:37.390 Now we'll be discussing in detail whenever a right session comes related to each of the status codes. 06:37.460 --> 06:41.630 I hope this has been informative for you and if you have any doubts, suggestions, questions, feel 06:41.630 --> 06:47.060 free to connect us at Twitter, Facebook or LinkedIn or email us at instructors at KP Labs. 06:47.510 --> 06:48.800 Thanks for watching.