1

1. The Basic HTTP GET/response interaction:

The basic HTTP get/response can be determined by opening a browser and visiting the website
http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file1.html . By observing this output
in the Wireshark we can answer several questions which are as follows:

Figure 1: Basic HTTP response of source and destination

1. Is your browser running HTTP version 1.0 or 1.1? What version of HTTP is the server
running?
Answer: My browser is running HTTP version 1.1 as shown in the below figure 2 and the HTTP
version of server is also 1.1 as shown in the below figure 3.

Figure 2: HTTP Version of my computer.

Figure 2: HTTP Version of the server.

2. What languages (if any) does your browser indicate that it can accept to the server?
Answer: My browser accepts only English language as shown in the below figure 3.

Figure 3: Language supported by the browser.

3. What is the IP address of your computer? Of the gaia.cs.umass.edu server?

The IP address of my computer is 10.0.0.192 and the IP address of gaia.cs.umass.edu server is
128.119.245.12 as shown in the below figure 4.

Figure 4: IP addresses of my computer and the server.

4. What is the status code returned from the server to your browser?
Answer:

Figure 5: Status code received from server.

The status received from the server to my browser is 200 as shown in the above figure 5.

5. When does the HTML file that you are retrieving is last modified at the server?
Answer: The HTML file retrieved was last modified at the server on Monday, 4 January 2016
06:59:01 GMT as shown in the below figure 6.

Figure 6: Modified HTML file.

6. How many bytes of content are being returned to your browser?

Answer: The size of the content returned to the browser is 128 bytes as shown in the below
figure 7.

Figure 7: Size of received HTML

7. By inspecting the raw data in the packet content window, do you see any headers within the
data that are not displayed in the packet-listing window? If so, name one.
Answer: No I didnt see any headers.

2. The HTTP CONDITIONAL GET/response interaction

8. Inspect the contents of the first HTTP GET request from your browser to the server. Do you
see an IF-MODIFIED-SINCE line in the HTTP GET?
Answer: No I didnt see any IF-MODIFIED-SINCE line in the HTTP GET.
9. Inspect the contents of the server response. Did the server explicitly return the contents of the
file? How can you tell?
Answer: The server has returned all the contents of the file as shown in the below figure 8 as line
based text data.

Figure 8: File received successfully

10. Now inspect the contents of the second HTTP GET request from your browser to the server.
Do you see an IF-MODIFIED-SINCE: line in the HTTP GET? If so, what information follows
the IF-MODIFIED-SINCE: header?
Answer: Yes, after refreshing the browser I got the information like If-Modified-Since: Mon, 04
Jan 2016 06:59:01 GMT as shown in the below figure 9.

Figure 9: If Modified Since Information obtained after refreshing.

11. What is the HTTP status code and phrase returned from the server in response to this second
HTTP GET? Did the server explicitly return the contents of the file? Explain.

Answer: The HTTP status code returned is 304 and the response phrase is not modified as
shown in the below figure 10. The browser did not returned any new file as the contents of the
file is already stored in the browsers cache.

Figure 10: Response of second HTTP.

10

3. Retrieving Long Documents:

Figure 11: Retrieving of Long Document Files

12. How many HTTP GET request messages were sent by your browser?
Answer: As seen in the figure 11, only one HTTP GET request was sent by the browser.

13. How many data-containing TCP segments were needed to carry the single HTTP response?
Answer: Totally there were 5 data containing TCP segments were needed.

14. What is the status code and phrase associated with the response to the HTTP GET request?
Answer: The status code that obtained is HTTP 200 Ok

11

15. Are there any HTTP status lines in the transmitted data associated with a TCP induced
Continuation?
Answer: There is no HTTP status line.
4. HTML Documents with Embedded Objects

Figure 12: Response with embedded objects

16. How many HTTP GET request messages were sent by your browser? To which Internet
addresses were these GET requests sent?
Answer: Totally three HTTP GET request messages sent by the browser like

104.16.56.23
107.22.193.119
128.119.240.90

12

17. Can you tell whether your browser downloaded the two images serially, or whether they were
downloaded from the two web sites in parallel? Explain.
Answer: The browser has downloaded the two images serially.
5 HTTP Authentication:
18. What is the servers response (status code and phrase) in response to the initial HTTP GET
message from your browser?
Answer: The servers response with the status code 401 and phrase is unauthorized as shown in
the below figure 13.

Figure 13: Servers Response

13

19. When your browsers sends the HTTP GET message for the second time, what new field is
included in the HTTP GET message?
Answer: The new field that included in the HTTP GET message for the second time is
Authorization: Basic d2lyZXNoYXJrLXN0dWRlbnRzOm5ldHdvcms=\r\n as shown in the
below figure14.

Figure 14: New Field obtained in the HTTP GET message