Wireshark Lab 2, Part 3: Retrieving Long Documents

Lab Video:

———————————————————————————————————————————————————————-

STEPS:

Step 1:Start up your web browser, and make sure your browser’s cache is cleared, as discussed above.

Step 2: Start up the Wireshark packet sniffer

Step 3: Enter the following URL into your browser http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file3.html Your browser should display the rather lengthy US Bill of Rights.

Step 4: Stop Wireshark packet capture, and enter “http” in the display-filter-specification window, so that only captured HTTP messages will be displayed.

———————————————————————————————————————————————————————-

QUESTIONS:

12. How many HTTP GET request messages did your browser send? Which packet number in the trace contains the GET message for the Bill or Rights?

• My browser only sent 1 HTTP GET request to the server. The Packet that contained the GET message was packet number 233.

13. Which packet number in the trace contains the status code and phrase associated with the response to the HTTP GET request?

• The packet that contains the status code and phrase which the server sent in response to the GET message was packet number 241.

14. What is the status code and phrase in the response?

• The code and phrase in the response was 200 OK, see the image from question 13.

15. How many data-containing TCP segments were needed to carry the single HTTP response and the text of the Bill of Rights?

• The data was sent in 5 TCP segments to the browser, then reassembled.