The bandwidth between the client and server (i.e., www.niiyaarnaan.com) is deemed to be 210 Mb/s and the round-trip time (RTT) is estimated to be 70 ms. Note that the RTT is the time it takes for a small packet to travel from client to server and then back to the client. Note also that a kilobyte (kB) is 1000 bytes, and a megabyte (MB) is 1000 kilobytes.


Please write down your answers to the following questions in milliseconds. Do not write the units however. For example, if your answer to a question is 34.5 ms, just write down 34.5 in the answer sheet.


1. The client (i.e., the browser) obtains from the server a 890 kB HTML file named 818413344.html with no embedded objects using the following (partial) HTTP request.
GET /818413344.html HTTP/1.1
Connection: close
Accept-Encoding: identity
Cache-control: no-store


Assuming that this HTML file was never accessed by the client prior to this request, what is the minimum time would it take the client, from the time the user clicked to access the URL corresponding to the HTML file, to get the file?


2. Had the (partial) HTTP request in the previous question (i.e., question 1) been the following:
GET /818413344.html HTTP/1.1
Connection: keep-alive
Accept-Encoding: identity
Cache-control: no-store


what is the minimum time would it take the client, from the time the user clicked to access the URL corresponding to the HTML file, to get the file? As before, assume that this HTML file was never accessed by the client prior to this request.


3. Had the (partial) HTTP request in question 1 been the following:
GET /818413344.html HTTP/1.1
Connection: keep-alive
Accept-Encoding: gzip
Cache-control: no-store


what is the minimum time would it take the client, from the time the user clicked to access the URL corresponding to the HTML file, to get the file? As before, assume that this HTML file was never accessed by the client prior to this request. You need to know that the server is able to compress selected content, if requested to do so, and it understands gzip compression. Our HTML file, 818413344.html, would compress to 89 kB when compressed with gzip.


Our HTML file, 818413344.html, is now modified, and the modifications include references to 9 PNG images. The size of the modified HTML file is 920 kB, and it would compress to 76 kB when compressed with gzip. The file sizes of the images, given in MB, are as follows: 1, 3, 1, 1, 3, 1, 1, 4, 3. The images are named image 0 through to image 8 for convenience, and the image file sizes here are given in that order. The following questions refer to this collection of images and the modified HTML file. Where applicable, requests could be sent back to back without having to wait for the responses.


4. This is essentially repeat of question 1, but with the 9 referenced images included. The (partial) HTTP request for the HTML file is shown below.
GET /818413344.html HTTP/1.1
Connection: close
Accept-Encoding: identity
Cache-control: no-store


You should assume similar requests to be sent by the client for the images sequentially. The client needs to process the HTML file to find out the URLs of each image, and this processing can start only after the client receives the entire file. For simplicity, assume that this processing time is negligible. How long would it take the client, from the time the user clicked to access the URL corresponding to the HTML file, to get the file and the images it refers to? Assume that none of files (HTML as well the images) have previously been accessed.


5. Now, repeat question 4 above with the following (partial) HTTP request for the HTML file:
GET /818413344.html HTTP/1.1
Connection: keep-alive
Accept-Encoding: identity
Cache-control: no-store


You should assume similar requests to be sent by the client for the images.


6. Now, repeat question 4 above with the following (partial) HTTP request for the HTML file:
GET /818413344.html HTTP/1.1
Connection: keep-alive
Accept-Encoding: gzip
Cache-control: no-store


You should assume similar requests to be sent by the client for the images.


7. This question is similar to question 4 above with the difference that some of the images, namely images 1, 2, 3, 8, are already in the client’s cache from a previous HTTP request. The rest of the images as well as the HTML file are not in its cache. Recalculate the time considering the cached images.


8. This question is similar to question 5 above with the difference that some of the images, namely images 1, 2, 3, 8, are already in the client’s cache from a previous HTTP request. The rest of the images as well as the HTML file are not in its cache. Recalculate the time considering the cached images.


9. This question is similar to question 6 above with the difference that some of the images, namely images 1, 2, 3, 8, are already in the client’s cache from a previous HTTP request. The rest of the images as well as the HTML file are not in its cache. Recalculate the time considering the cached images.


✍ The expected learning outcomes of this assignment are as follows.


Being able to calculate latencies involved in the HTTP transactions, assuming a simple model.
An appreciation of how compression can help to reduce latency.
An appreciation of how caches can positively influence data transfers.


Please explain each answer to each question step by step and in great detail

please each answer step by step and in great detail, the format the answers similar to this at the very end:
AUID: 987654321
1: 42.42
2: 42.42
3: 42.42
4: 42.42
5: 42.42
6: 42.42
7: 42.42
8: 42.42
9: 42.42