Wireshark Lab HTTP Solution

Wireshark Lab: HTTP SOLUTION The following screen shots showing the HTTP GET and HTTP reply answer these questions: 1. Is your browser running HTTP version 1.0 or 1.1? What version of HTTP is the server running? 2. What languages (if any) does your browser indicate that it can accept to the server? 3. What is the IP address of your computer? Of the gaia.cs.umass.edu server? 4. What is the status code returned from the server to your browser? 5. When was the HTML file that you are retrieving last modified at the server? 6. How many bytes of content are being returned to your browser? 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 don’t see any in the HTTP Message below Client IP address Gaia server IP address Client running http 1.1 languages accepted Return status: server running http document last modified content: 128 2. The HTTP CONDITIONAL GET/response interaction Here’s a screenshot after doing the two identical HTTP GETs: First GET, then a reply, then another identical GET, then a reply (304 not modified) Answer the following questions: 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? 9. Inspect the contents of the server response. Did the server explicitly return the contents of the file? How can you tell? 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? 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. Here are the four captures packets (two GETs and two REPLIES, in chronological order): There is no IF-MODIFIED-SINCE in the first GET text returned in response to first GET 2nd GET has IF-MODIFED-SINCE The file has not been modified! So the text of the file is NOT returned in the HTTP message 3. Retrieving Long Documents In our answer below, we use the http-ethereal-trace-3 packet trace file. The HTTP GET for the long document is packet 8 in the trace (at t=4.623732); the HTTP OK reply is packet 14 (at t=6.680432). The HTTP repl7 carrying the text of the Bill of Rights are packets 10, 11, and 13. If you look into the ASCII content of packet 10, you can see the beginning of the text of the Bill or Rights. Note that packet 12 is a client-to-server TCP ACK. Answer the following questions: 12. How many HTTP GET request messages did your browser send? Answer: 1. Which packet number in the trace contains the GET message for the Bill or Rights? Answer: 8. 13. Which packet number in the trace contains the status code and phrase associated with the response to the HTTP GET request? Answer: packet 10. 14. What is the status code and Phrase in the response? Answer: 200 (OK) 15. How many data-containing TCP segments were needed to carry the single HTTP response and the text of the Bill of Rights? Answer: three packets (10, 11, 13 in the trace) 4. HTML Documents with Embedded Objects In our answers below, we use the http-ethereal-trace-4 packet trace file. Answer the following questions: 16. How many HTTP GET request messages did your browser send? Answer: there were three HTTP GET messages sent: packet 10 in the trace (to get the base file), packet 17 (to get the Pearson logo) and packet 20 (to get the 5th edition textbook cover). To which Internet addresses were these GET requests sent? Each of these three GET messages were sent to different IP addresses! Packet 10 was sent to 128.119.245.12, packet 17 to 165.193.123.218, and packet 20 to 134.241.6.82. 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 downloads occurred in parallel. Note that the two GET messages for the images are in packets 17 and 20. The 200OK reply containing the images sow up as packets 25, and 54. Thus the request for the second image file (packet 20) was made BEFORE packet 25, the first image file was received. 5 HTTP Authentication Finally, let’s try visiting a web site that is password-protected and examine the sequence of HTTP message exchanged for such a site. The URL http://gaia.cs.umass.edu/wireshark-labs/protected_pages/HTTP-wireshark-file5.html is password protected. The username is “wireshark-students” (without the quotes), and the password is “network” (again, without the quotes). So let’s access this “secure” password-protected site. Do the following: • Make sure your browser’s cache is cleared, as discussed above, and close down your browser. Then, start up your browser • Start up the Wireshark packet sniffer • Enter the following URL into your browser http://gaia.cs.umass.edu/wireshark-labs/protected_pages/HTTP-wiresharkfile5.html Type the requested user name and password into the pop up box. • Stop Wireshark packet capture, and enter “http” in the display-filter-specification window, so that only captured HTTP messages will be displayed later in the packet-listing window. • (Note: If you are unable to run Wireshark on a live network connection, you can use the http-ethereal-trace-5 packet trace to answer the questions below; see footnote 2. This trace file was gathered while performing the steps above on one of the author’s computers.) Now let’s examine the Wireshark output. You might want to first read up on HTTP authentication by reviewing the easy-to-read material on “HTTP Access Authentication Framework” at http://frontier.userland.com/stories/storyReader$2159 Answer the following questions: 18. What is the server’s response (status code and phrase) in response to the initial HTTP GET message from your browser? Answer: Packet 6 in the trace contains the first GET and packet 9 contains the REPLY. The server’s in packet 9 is: 401 Authorization Required 19. When your browser’s sends the HTTP GET message for the second time, what new field is included in the HTTP GET message? Answer: The HTTP GET includes the Authorization: Basic: field