Lab 2. All datagrams related to favicon.ico had been ignored. Diagram 1. Diagram 2

Similar documents
Wireshark Lab: HTTP SOLUTION

Wireshark HTTP. Introduction. The Basic HTTP GET/response interaction

Wireshark Lab: HTTP v6.1

Wireshark Lab: HTTP. 1. The Basic HTTP GET/response interaction

CSE4344 Project 2 (Spring 2017) Wireshark Lab: HTTP

Project points. CSE422 Computer Networking Spring 2018

Wire Shark Lab1. Intro

Department Of Computer Science

Problem Set 9 Due: Start of class, December 4

Lecture 7b: HTTP. Feb. 24, Internet and Intranet Protocols and Applications

Lab Assignment 3 for ECE374

Computer communication EDA343/DIT420 Lab 1

Wireshark Lab: Ethernet and ARP v6.01

Browser behavior can be quite complex, using more HTTP features than the basic exchange, this trace will show us how much gets transferred.

Wireshark Lab: Getting Started

Application Layer. Applications and application-layer protocols. Goals:

Wireshark Lab: TCP v7.0

Getting Started. 1 Earlier versions of these labs used the Ethereal packet analyzer. In May 2006, the developer of Ethereal

COMPUTER NETWORK. Homework #1. Due Date: March 29, 2017 in class

Lab Two Using Wireshark to Discover IP NAME:

Problem Set 7 Due: Start of Class, November 2

Data Communication EDA344, DIT420 Description of Lab 1 and Optional Programming HTTP Assignment

1-1. Switching Networks (Fall 2010) EE 586 Communication and. September Lecture 10

Wireshark Lab: Getting Started v7.0

Wireshark Lab: Getting Started v6.0

TCP/IP Networking Basics

Homework 4 assignment for ECE374 Posted: 04/06/15 Due: 04/13/15

Ethereal Lab: Getting Started

The trace file is here:

Network II Lab 03 Part 01: Ping command in simula on mode

Exploring TCP and UDP based on Kurose and Ross (Computer Networking: A Top-Down Approach) May 15, 2018

Before beginning this lab, you ll probably want to review sections 3.5 and 3.7 in the text. 1

CSE434 Computer Networks (FALL, 2009) Programming Assignment 2 Due: Wed, October 7, 2009

Wireshark Lab: Getting Started v7.0

Web, HTTP and Web Caching

Wireshark Lab: Getting Started v6.0

Ethereal Lab: Getting Started

Lab Assignment 4 ECE374 Spring Posted: 03/22/18 Due: 03/29/18. In this lab, we ll take a quick look at the ICMP and IP protocols.

Computer Systems and Networks

9. Wireshark I: Protocol Stack and Ethernet

Before beginning this lab, you ll probably want to review sections 3.5 and 3.7 in the text.

Computer Network Midterm Explain Internet protocol stack (1% each layer s name, 1% each layer s functions, 10% total)

Use of the TCP/IP Protocols and the OSI Model in Packet Tracer

EE 122: HyperText Transfer Protocol (HTTP)

Lab: 2. Wireshark Getting Started

Objectives: (1) To learn to capture and analyze packets using wireshark. (2) To learn how protocols and layering are represented in packets.

Application Level Protocols

University of Maryland Baltimore County Department of Information Systems Spring 2015

Computer Networks - A Simple HTTP proxy -

Introduction to Internet, Web, and TCP/IP Protocols SEEM

UNI CS 3470 Networking Project 5: Using Wireshark to Analyze Packet Traces 12

HyperText Transfer Protocol

Application Protocols and HTTP

Computer Systems and Networks

Problem Set 6 Due: Start of Class, October 26

CSCI4211: Introduction to Computer Networks Fall 2017 Homework Assignment 1

Lab Exercise Protocol Layers

5. Write a capture filter for question 4.

CS 356 Lab #1: Basic LAN Setup & Packet capture/analysis using Ethereal

EE586 Homework and Laboratory #5 Due November 3, 2010

a. (4pts) What general information is contained in a LSR-PDU update that A might send?

Lecture 6 Application Layer. Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it

HTTP Authentication API

Goals - to become acquainted with Wireshark, and make some simple packet captures and observations

CMSC 332 Computer Networking Web and FTP

Black Box DCX3000 / DCX1000 Using the API

0 0& Basic Background. Now let s get into how things really work!

QoS attributes of a packet. Quality of service (QoS) Packet latency affects transport service QoS. Transport services.

Application Layer Introduction; HTTP; FTP

TACACS Support APIs. curl -k -v -u "admin:cisco123" -H Accept:application/vnd.yang.data+xml -H ContentType:application/vnd.yang.

Submit your captured trace file from the TCP lab exercise (Section 1 describes how this can be done).

Lab Exercise UDP. Objective. Requirements. Step 1: Capture a Trace

Router and ACL ACL Filter traffic ACL: The Three Ps One ACL per protocol One ACL per direction One ACL per interface

SC/CSE 3213 Winter Sebastian Magierowski York University CSE 3213, W13 L8: TCP/IP. Outline. Forwarding over network and data link layers

Network Reference Models

World-Wide Web Protocols CS 571 Fall Kenneth L. Calvert All rights reserved

HTTP Server Application

WEB TECHNOLOGIES CHAPTER 1

Wireshark Lab: Getting Started v6.0 Supplement to Computer Networking: A Top-Down Approach, 6th ed., J.F. Kurose and K.W. Ross

Wireshark Lab: IP v6.0

Wireshark Lab: Getting Started

Wireshark intro. Introduction. Packet sniffer

CS 43: Computer Networks. Layering & HTTP September 7, 2018

Wireshark Lab: Getting Started

TCP/IP Networking An Example

CS4/MSc Computer Networking. Lecture 3: The Application Layer

Last Lecture. methods. ! How to send data from end to end: two switching. ! Packet loss and delay in a packet switched network. !

Homework 2 50 points. CSE422 Computer Networking Spring 2018

New York University Computer Science Department Courant Institute of Mathematical Sciences

Review of Previous Lecture

Session 8. Reading and Reference. en.wikipedia.org/wiki/list_of_http_headers. en.wikipedia.org/wiki/http_status_codes

Networking Fundamentals

COSC 2206 Internet Tools. The HTTP Protocol

BSc Year 2 Data Communications Lab - Using Wireshark to View Network Traffic. Topology. Objectives. Background / Scenario

COMP416 Lab (7) IEEE Daoyuan

Web Client And Server

Getting Wireshark. Detailed installing steps can be found on the Internet, so this tutorial won t cover this part.

Configuring IP SLAs HTTP Operations

Produced by. Mobile Application Development. Higher Diploma in Science in Computer Science. Eamonn de Leastar

Chapter 19. Protocol architecture. Summary. Key ideas. Copyright 1998, David G. Messerschmitt. All rights reserved. by David G.

Transcription:

Lab 2 All datagrams related to favicon.ico had been ignored. Diagram 1 Diagram 2 1. Is your browser running HTTP version 1.0 or 1.1? What version of HTTP is the server running?

According to the diagram 1, the browser is running HTTP 1.1. According to the diagram 2, the server is also running HTTP 1.1. 2. What languages (if any) does your browser indicate that it can accept to the server? According to the diagram 1, the accepting languages are en US,en. 3. What is the IP address of your computer? Of the gaia.cs.umass.edu server? According to Diagram 1, my computer s IP address is 192.168.1.11 and the IP address of gaia.cs.umass.edu is 128.119.245.12. 4. What is the status code returned from the server to your browser? According to the diagram 2, the status code returned from the server to my browser is 200. 5. When was the HTML file that you are retrieving last modified at the server? According to the diagram 2, the last modified time is Mon, 10 Feb 2014 07:18:01 GMT. 6. How many bytes of content are being returned to your browser? According to the diagram 2, Content Length: 128 bytes 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. No, there is no more headers below.

Diagram 3 Diagram 4

Diagram 5 Diagram 6

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? According to the Diagram 3, there is no IF MODIFIED SINCE line in the first HTTP GET, but according to the Diagram 4, IF MODIFIED SINCE is found in the second HTTP GET (the web page cached locally, asking the server side, the local cache need to be updated or not). 9. Inspect the contents of the server response. Did the server explicitly return the contents of the file? How can you tell? According to Diagram 5, the server explicitly return the contents of the file, but according to the Diagram 6, the server did not explicitly return the contents of the file since the file had not been modified. 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? According to the Diagram 4, IF MODIFIED SINCE is found in the second HTTP GET (the web page cached locally, asking the server side, the local cache need to be updated or not). According to the Diagram 6, the server returning a 304 not modified 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. According to the Diagram 6. The HTTP status code is 304 Not Modified and the server did not explicitly return the contents of the file since the file was cached locally.

For Question 12 19, the answers are based on the author s trace file. Diagram 7 12. How many HTTP GET request messages did your browser send? Which packet number in the trace contains the GET message for the Bill of Rights? According to the Diagram 7, only 1 HTTP GET request was sent by my browser and the packet 8 in the trace contains the GET message for the Bill of Rights. 13. Which packet number in the trace contains the status code and phrase associated with the response to the HTTP GET request? Connects in packet 10

The first response packet (PDU) from the server, packet 10 contains the status code and phrase. 200 OK 14. What is the status code and phrase in the response? 15. How many data containing TCP segments were needed to carry the single HTTP response and the text of the Bill of Rights? According to the diagram 7, 3 TCP segments (10, 11 and 13) were needed to carry the single HTTP response and the text of the Bill of Rights. Diagram 8 16. How many HTTP GET request messages did your browser send? To which Internet addresses were these GET requests sent? According to the Diagram 8, the browser sent 3 HTTP GET request messages. Packet 10 was sent to 128.119.245.12, packet 17 was sent to 165.193.123.218, and packet 20 was sent 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 Two images were downloaded in parallel. According to diagram 8, the HTTP GET requests for two images were sent using packet 17 and 20, and the response packets were 25 and 54 which means the request for the second image was made before the first image was received.

Diagram 9 18. What is the server s response (status code and phrase) in response to the initial HTTP GET message from your browser? According to the diagram 9, the initial HTTP GET message should be packet 6 and the packet 9 is the response to the packet 6. Thus the server s response 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? The new field of the HTTP GET message is the Authorization: Basic.