WEBVTT 00:00.170 --> 00:03.950 Hey, everyone, and welcome back to the Knowledge Portal Video series. 00:03.980 --> 00:08.340 Now, in the earlier lecture we discussed about the cache control header. 00:08.360 --> 00:15.200 We also looked into the difference between two files where you have my c dot jpg, which does not have 00:15.200 --> 00:21.750 any cache control headers and you have no store dot PNG where you have a cache control header. 00:21.770 --> 00:31.820 So what a web server is saying to the client that this specific file no store dot PNG should not be 00:31.820 --> 00:33.380 stored in the cache. 00:33.860 --> 00:41.660 And when you talk about my c dot jpg, there is no explicitly mentioned by the web server on what to 00:41.660 --> 00:42.460 do with this file. 00:42.470 --> 00:50.810 So a browser may or may not store this file in the cache depending upon the browser caching configuration. 00:50.810 --> 00:52.400 So let's do one thing. 00:52.400 --> 00:57.230 Let's try this out in our browser so that we can know how exactly this would work. 00:58.370 --> 01:03.980 So I'll copy this file and I'll paste it in my Google Chrome. 01:04.520 --> 01:09.140 And if I press enter, you have a my c dot jpg file. 01:09.170 --> 01:14.060 However, now if you go to about cache, let's try this out. 01:16.300 --> 01:24.040 You will see there is a file called as MCD dot jpg, which is stored in the cache of my Google Chrome. 01:24.370 --> 01:25.180 Perfect. 01:25.180 --> 01:32.590 So now let's copy the no store dot PNG file. 01:36.490 --> 01:46.330 I'll just copy the URL and let me paste it here. 01:46.330 --> 01:49.930 And here you have no store dot PNG file. 01:49.930 --> 01:51.700 Now again, this is an image file. 01:51.730 --> 02:02.410 So let's open about cache again and let's verify whether we have MCD or JPG, but we could not find 02:02.410 --> 02:03.820 the no store dot PNG. 02:03.910 --> 02:11.110 However, just to verify if we are not missing out, I'll do a ctrl f to search and I'll say no store 02:11.680 --> 02:13.780 dot PNG. 02:14.680 --> 02:18.280 So you don't really have a file. 02:18.280 --> 02:21.250 So this is just the Google dot Google result. 02:21.250 --> 02:22.640 So just ignore this. 02:22.660 --> 02:25.660 However, we are looking for a file. 02:25.660 --> 02:29.250 You can actually copy the URL to get a better result. 02:29.260 --> 02:33.250 So when you copy the MC dot jpg url, you are getting it. 02:33.280 --> 02:41.380 However, when you copy the URL of no store dot PNG, let me check this out. 02:42.580 --> 02:44.830 You see, you are not getting any result. 02:44.830 --> 02:52.260 So one important thing to remember is that browser will store the result as a key pair. 02:52.270 --> 02:55.030 Now I'll give you one simple example. 02:55.030 --> 03:04.120 So I have about cache and if you look into the caching entries, so let me open one of them. 03:04.960 --> 03:14.740 So you see the key is basically the URL, entire URL and this is the reason why the key is the entire 03:14.740 --> 03:15.990 URL which is stored. 03:16.000 --> 03:26.720 So, so when you just copy the URL, you can find the URL as stored as a key in the caching entry. 03:26.900 --> 03:27.440 Okay. 03:27.470 --> 03:32.930 I hope this specific concept is much more clear to you. 03:32.930 --> 03:36.080 So let's do one thing. 03:36.440 --> 03:39.040 This is a small lecture which I wanted to show you. 03:39.050 --> 03:43.600 Go ahead and try this out from your site, see how exactly it will work. 03:43.610 --> 03:49.940 I'll make sure that these files exist in the server so you can do a practice from your side as well. 03:49.940 --> 03:57.410 And in the next lecture, what we will be doing is we will be configuring our own cache control headers 03:57.410 --> 04:01.460 in our Docker engine that we have been working with. 04:01.460 --> 04:08.300 So this is it about this lecture, small lecture, but I hope you got the overall concept related to 04:08.300 --> 04:12.950 the Node store header and I look forward to see you in the next lecture.