CPSC 471-05 HTTP traffic

HTTP请求状态码对照表,系统自定义code释义 当浏览者访问一个网页时,浏览者的浏览器会向网页所在服务器发出请求。当浏览器接收并显示网页前,此网页所在的服务器会返回一个包含HTTP状态码的信息头(server header)用以响应浏览器的请求。HTTP状态码的英文为HTTP Status Code。稍微记录一下,避免忘记200- 请求成功301- 资源(网页等)被永久转移到其它URL404- 请求的资源(网页等)不存在500- 内部服务器错误code中文描述200接口正常返回,返回正确信息400接口正常返回,返回错误提示。 阅读详情


CPSC 471-05 Assignment
Introduction 
At the heart of the communication involving a browser and a server, RFC 2616 defines the fun damental protocol that governs interactions between internet devices. The result was known as 
the HTTP protocol. In this assignment, we will capture HTTP traffic using Wireshark packet sniff er and examine various HTTP header information and their applications in details.
HTTP provides a very important feature that enables browser caching mechanism. The results
are improved user’s experiences, significant reduction in communication link bandwidth re quirement and expenses. We will observe HTTP caching mechanism interactions in details.
Finally, the benefit of network architectural design layering approach becomes clear when we 
develop internet-enabled applications that seamlessly exchange data between host devices 
across the internet using socket programming.
Required Softwares 
Wireshark 4.4.0 or newer
Python 3.12.6 or newer.
Submission 
Submit in Canvas only. Submission using other methods outside Canvas will not be accepted.
For this assignment, Canvas was set up to only accept .zip file.
Reminders:
 Click on your submitted file in Canvas to download it back to your PC, and verify that the 
submitted file is not corrupted and that it contains the exact files required from you for 
this assignment.
 Give yourself plenty of time to accomplish this. Running out of time, or submitting an in correct file, corrupted file will be treated as No Submission.
File Size Limitation 
Maximum allowable submission file size is 10MB. A penalty of 10% will be deducted for each 10 
MB in excess of the allowed 10 MB limit.
Page 1 of 19
Page 2 of 19
Submission Grace Period 
According to our class syllabus you have a 24-hour window after the due-date time to submit 
before the assignment closing-date time with a 10% late penalty.
Note: The assignment due date and time, and the assignment closing date and time are clearly 
shown on Canvas. Once the assignment is closed you can no longer submit.
What To Submit 
Submit one zip file using naming convention fullname.zip in Canvas.
The zip file shall contain all below listed files and must follow the naming convention as shown:
(1) One PDF report file xxReport.pdf.
Note: This must be a Portable Document Format (PDF) file. Word documents are vul nerable to macro viruses and may not be graded.
(2) Wireshark capture file from Part 1a xxP1a.pcapng
(3) Wireshark capture file from Part 1b xxP1b.pcapng
(4) Wireshark capture file from Part 1c xxP1c.pcapng
(5) Wireshark capture file from Part 1d xxP1d.pcapng
(6) Wireshark capture file from Part 1e xxP1e.pcapng
(7) Python UDP client code file from Part 2a xxP2a.py
(8) Python UDP server code file from Part 2b xxP2b.py
(9) Python UDP server code file from Part 2c xxP2c.py
where xx is your first name and last name initials.
Hints: Use the standard compression utility already available from your PC Operating System to 
produce the zip file. That way the submitted zip file can be opened for grading using standard 
Windows OS built-in uncompress utility.
 
Page 3 of 19
Part 1: Analyzing HTTP Messages using Wireshark 
Part 1a: Basic HTTP GET/response interaction 
Let’s begin our exploration of HTTP by downloading a very simple HTML file - one that is very 
short and contains no embedded objects. Do the following:
 Start up your web browser.
 Start up the Wireshark packet sniffer. Enter “http” (just the letters, not the quotation 
marks) in the display-filter-specification window, so that only captured HTTP messages 
will be displayed later in the packet-listing window. 
 Wait a bit more than one minute (we’ll see why shortly), and then begin Wireshark 
packet capture.
 Quickly enter the following to your browser
http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file1.html
Your browser should display the very simple, one-line HTML file.
 Quickly stop Wireshark packet capture and save the Wireshark capture in file 
xxP1a.pcapng.
Very Important notes on keeping captured files small:
 Start capture only when ready
 Stop capture immediately after you got what you wanted
Page 4 of 19
Your Wireshark window should look similar to the window shown in Figure 1. 
Figure 1: Wireshark Display after http://gaia.cs.umass.edu/wireshark-labs/ HTTP-wireshark file1.html has been retrieved by your browser.
The example in Figure 1 shows in the packet-listing window that two HTTP messages were cap tured: the GET message (from your browser to the gaia.cs.umass.edu web server) and the re sponse message from the server to your browser. The packet-contents window shows details of 
the selected message (in this case the HTTP OK message, which is highlighted in the packet listing window). Recall that since the HTTP message was carried inside a TCP segment, which 
was carried inside an IP datagram, which was carried within an Ethernet frame, Wireshark dis plays the Frame, Ethernet, IP, and TCP packet information as well. We want to minimize the 
amount of non-HTTP data displayed, so make sure the boxes at the far left of the Frame, Ether net, IP and TCP information have a plus sign or a right-pointing triangle (which means there is 
hidden, not displayed information), and the HTTP line has a minus sign or a down-pointing trian gle (which means that all information about the HTTP message is displayed).
(Note: You should ignore any HTTP GET and response for favicon.ico. If you see a reference to this file, it 
is your browser automatically asking the server if it (the server) has a small icon file that should be dis played next to the displayed URL in your browser. We’ll ignore references to this pesky file.)
 
Page 5 of 19
Part 1a Items To Submit 
Include the Wireshark capture file xxP1a.pcapng in the submission zip file.
In the PDF file report, create a section called Part 1a – Basic HTTP GET/response interaction.
Include answers for Part 1a questions below.
By looking at the information in the HTTP GET and response messages, answer the following 
questions.
When answering each question, you should include the screen capture of the GET and response 
messages and graphically circle or highlight to indicate where within the message the requested 
information came from.
(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.
In your answer to question 5 above, you might have been surprised to find that the document 
you just retrieved was last modified within a minute before you downloaded the document. 
That’s because (for this particular file), the gaia.cs.umass.edu server is setting the file’s last modified time to be the current time and is doing so once per minute. Thus, if you wait a minute 
between accesses, the file will appear to have been recently modified, and hence your browser 
will download a “new” copy of the document.
 
Page 6 of 19
Part 1b: The HTTP CONDITIONAL GET/response interaction 
Recall from Section 2.2.5 of the textbook, that most web browsers perform object caching and 
thus perform a conditional GET when retrieving an HTTP object. Before performing the steps 
below, make sure your browser’s cache is empty by clearing its cache. Now perform the follow ing:
 Start up your web browser, and make sure your browser’s cache was cleared, as dis cussed above.
 Begin Wireshark capture
 Enter the following URL into your browser
http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file2.html
Your browser should display a very simple five-line HTML file. 
 Quickly enter the same URL into your browser again (or simply select the refresh button 
on your browser)
 Stop Wireshark 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. 
Save the Wireshark capture in file xxP1b.pcapng.
Part 1b Items To Submit 
Include the Wireshark capture file xxP1b.pcapng in the submission zip file.
In the PDF file report, Create a section called Part 1b: The HTTP CONDITIONAL GET/response 
interaction. Include answers for Part 1b questions below:
(1) 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?
(2) Inspect the contents of the server response. Did the server explicitly return the contents 
of the file? How can you tell?
(3) 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 infor mation follows the “IF-MODIFIED-SINCE:” header?
(4) 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.
 
Part 1c: Retrieving Long Documents 
In our examples thus far, the documents retrieved have been simple and short HTML files. Let’s 
next see what happens when we download a long HTML file. Do the following:
 Start up your web browser, and make sure your browser’s cache is cleared.
 Begin Wireshark capture
 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.
 Stop Wireshark capture and enter “http” in the display-filter-specification window, so 
that only captured HTTP messages will be displayed. Save the capture in file 
xxP1c.pcapng
In the packet-listing window, you should see your HTTP GET message, followed by a multiple packet TCP response to your HTTP GET request. This multiple-packet response deserves a bit of 
explanation. Recall from Section 2.2 (see Figure 2.9 in the textbook) that the HTTP response 
message consists of a status line, followed by header lines, followed by a blank line, followed by 
the entity body. In the case of our HTTP GET, the entity body in the response is the entire re quested HTML file. In our case here, the HTML file is rather long, and at 4500 bytes is too large 
to fit in one TCP packet. The single HTTP response message is thus broken into several pieces by 
TCP, with each piece being contained within a separate TCP segment (see Figure 1.24 in the 
textbook). In recent versions of Wireshark, Wireshark indicates each TCP segment as a separate 
packet, and the fact that the single HTTP response was fragmented across multiple TCP packets 
is indicated by the “TCP segment of a reassembled PDU” in the Info column of the Wireshark
display. Earlier versions of Wireshark used the “Continuation” phrase to indicate that the entire 
content of an HTTP message was broken across multiple TCP segments. We stress here that 
there is no “Continuation” message in HTTP!
Part 1c Items To Submit 
Include the Wireshark capture file xxP1c.pcapng in the submission zip file.
In the PDF file report, Create a section called Part 1c: Retrieving Long Documents. Include an swers for Part 1c questions below.
(1) 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?
(2) Which packet number in the trace contains the status code and phrase associated with 
the response to the HTTP GET request?
(3) What is the status code and phrase in the response?
Page 7 of 19
Page 8 of 19
(4) How many data-containing TCP segments were needed to carry the single HTTP re sponse and the text of the Bill of Rights?
 
Page 9 of 19
Part 1d: HTML Documents with Embedded Objects 
Now that we’ve seen how Wireshark displays the captured packet traffic for large HTML files, 
we can look at what happens when your browser downloads a file with embedded objects, i.e., 
a file that includes other objects (in the example below, image files) that are stored on another 
server(s).
Perform the following:
 Start up your web browser, and make sure your browser’s cache is cleared
 Begin Wireshark capture
 Enter the following URL into your browser
http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file4.html
Your browser should display a short HTML file with two images. These two images are 
referenced in the base HTML file. That is, the images themselves are not contained in 
the HTML; instead, the URLs for the images are contained in the downloaded HTML file. 
As discussed in the textbook, your browser will have to retrieve these logos from the in dicated web sites. Our publisher’s logo is retrieved from the gaia.cs.umass.edu web 
site. The image of the cover for our 5th edition (one of our favorite covers) is stored at 
the caite.cs.umass.edu server. (These are two different web servers inside 
cs.umass.edu).
 Stop Wireshark capture and enter “http” in the display-filter-specification window, so 
that only captured HTTP messages will be displayed. Save the capture in file 
xxP1d.pcapng
Part 1d Items To Submit 
Include the Wireshark capture file xxP1d.pcapng in the submission zip file.
In the PDF file report, Create a section called Part 1d: HTML Documents with Embedded Ob jects. Include answers for Part 1d questions below.
(1) How many HTTP GET request messages did your browser send? To which Internet ad dresses were these GET requests sent?
(2) Can you tell whether your browser downloaded the two images serially, or whether 
they were downloaded from the two web sites in parallel? Explain.
 
Part 1e: 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 pass word 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, and close your browser. Then, start up your 
browser
 Begin Wireshark capture
 Enter the following URL into your browser
http://gaia.cs.umass.edu/wireshark-labs/protected_pages/HTTP-wireshark-file5.html
Type the requested username and password into the pop up box.
 Stop Wireshark 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. 
Save the capture in file xxP1e.pcapng
Now let’s examine the Wireshark output. You might want to first read up on HTTP authentica tion by reviewing the easy-to-read material on “HTTP Access Authentication Framework” at 
http://frontier.userland.com/stories/storyReader$2159
Part 1e Items To Submit 
Include the Wireshark capture file xxP1e.pcapng in the submission zip file.
In the PDF file report, Create a section called Part 1e: HTTP Authentication. Include answers for 
Part 1e questions below.
(1) What is the server’s response (status code and phrase) in response to the initial HTTP 
GET message from your browser?
(2) When your browser’s sends the HTTP GET message for the second time, what new field 
is included in the HTTP GET message?
The username (wireshark-students) and password (network) that you entered are encoded in 
the string of characters (d2lyZXNoYXJrLXN0dWRlbnRzOm5ldHdvcms=) following the “Author ization: Basic” header in the client’s HTTP GET message. While it may appear that your 
username and password are encrypted, they are simply encoded in a format known as Base64 
format. The username and password are not encrypted! To see this, go to 
http://www.motobit.com/util/base64-decoder-encoder.asp and enter the base64-encoded 
Page 10 of 19
Page 11 of 19
string d2lyZXNoYXJrLXN0dWRlbnRz and decode. Voila! You have translated from Base64 en coding to ASCII encoding, and thus should see your username! To view the password, enter the 
remainder of the string Om5ldHdvcms= and press decode. Since anyone can download a tool 
like Wireshark and sniff packets (not just their own) passing by their network adaptor, and any one can translate from Base64 to ASCII (you just did it!), it should be clear to you that simple 
passwords on WWW sites are not secure unless additional measures are taken. 
 
Page 12 of 19
Part 2: Socket Programming 
Part 2a: UDP Pinger with No Delay and No Loss 
In this portion, you will learn the basics of socket programming for UDP in Python. You will learn 
how to send and receive datagram packets using UDP sockets and, how to set a proper socket 
timeout. Throughout the lab, you will gain familiarity with a Ping application and its usefulness 
in computing statistics such as packet loss rate.
You will first study a simple Internet ping server written in the Python and implement a corre sponding client. The functionality provided by these programs is like the functionality provided 
by standard ping programs available in modern operating systems. However, these programs
use a simpler protocol, UDP, rather than the standard Internet Control Message Protocol (ICMP) 
to communicate with each other. The ping protocol allows a client machine to send a packet of 
data to a remote machine, and have the remote machine return the data back to the client un changed (an action referred to as echoing). Among other uses, the ping protocol allows hosts to 
determine round-trip times to other machines.
You are given the complete code for the Ping server in the next subsection. Your task is to write 
the UDP Ping client.
Server Code 
You are provided with the following code which fully implements a ping server. You need to run 
this code before running your client program. Your client code in this portion of the assignment
will be graded using this exact same server code (do not modify it for this portion of the assign ment).
You should study this code carefully, as it will help you write your ping client code.
# udppingserver_no_loss.py
from socket import *
# Create a UDP socket
serverSocket = socket(AF_INET, SOCK_DGRAM)
# Assign IP address and port number to socket
serverSocket.bind(('', 12000))
while True:
# Receive the client packet along with the address it is coming from
message, address = serverSocket.recvfrom(1024)
# The server responds
serverSocket.sendto(message, address)
The server sits in an infinite loop listening for incoming UDP packets. When a packet comes in, 
the server simply sends it back to the client.
Page 13 of 19
Client Code 
You task is to implement the client program as explained below.
The client should send a specified number of pings to the server. Because UDP is an unreliable 
protocol, a packet sent from the client to the server may be lost in the network, or vice versa. 
For this reason, the client cannot wait indefinitely for a reply to a ping message. You should get 
the client wait up to one second for a reply; if no reply is received within one second, your client 
program should assume that the packet was lost during transmission across the network. You 
will need to look up the Python documentation to find out how to set the timeout value on a 
datagram socket.
Requirements for Client Code 
The client program should:
 send the ping message using UDP
 print the response message from server if any was received
 calculate and print the round-trip time (RTT), in milliseconds, of each packet if the server 
responses
 otherwise, print “Request timed out”
 provide a sumAlice report at the end (of all pings) which includes:
o minimum RTT in milliseconds,
o maximum RTT in milliseconds,
o average RTT in milliseconds,
o percentage packet loss rate
You should run the udppingserver_no_loss.py on your machine and test your client by sending
packets to the localhost.
Ping Message Format 
The client ping message is a one line, consisting of ASCII characters and must be in the follow ing format:
firstname ping_number date_and_time
where:
firstname is your first name.
ping_number starts at 1 and progresses to total number of pings for each successive ping mes sage sent by the client, and time is the time when the client sends the message.
For example: The following is a sample display from the client program for student Alice.
Alice 1: server reply: Alice 1 Fri Sep 13 09:00:15 2024, RTT = 3.99 ms
Alice 2: server reply: Alice 2 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Page 14 of 19
Notes: the blue text represents the response from the server upon receiving the ping message 
(which is the message the server received from the client). The other texts are from the client 
itself.
Refer to the Appendix section on the last page for samples and required data format.
Part 2a Items To Submit 
Include Part 2a Python client code file xxP2a.py in the submission zip file.
In the PDF file report, create a section called Part 2a – UDP Pinger with No Delay and No Loss. 
Include the followings:
(1) Describe the operation of your UDP Pinger, for example how it works.
(2) Explain how to specify the timeout value for a datagram socket. Provide an example.
(3) Explain how to run your code, i.e., command line and any applicable parameter(s)
a. Include run-time screen captures for a sequence consists of 10 pings
Refer to the Appendix section on the last page for samples and required data for mat.
(4) Paste the Python client code listing text (must be text, not a screenshot graphic of the 
text) in the report. Use consolas font size 10 or equivalent monospace font. The use of 
the monospace font is to clearly show indentations in your code.
 
Page 15 of 19
Part 2b: UDP Pinger with Delays 
Delays 
Our experiment so far has been on a local host running both server and client programs, and 
therefore we saw zero delays. In this portion of the assignment, you are asked to modify the 
server code to simulate random RTT delays ranging from 10ms to 20ms.
Hint: Create a variable which holds a randomized integer to determine the delay amount.
Part 2b Items To Submit 
Include Part 2b Python server code file xxP2b.py in the submission zip file.
In the PDF file report, create a section called Part 2b – UDP Pinger No Loss, with Delays. Include 
the followings:
(1) Describe the operation of your UDP Ping Server and explain how it simulates 10ms to 
20ms RTT delays.
(2) Explain how to run your code, i.e., command line and any applicable parameter(s)
a. Include run-time screen captures for a sequence consists of 10 pings
Refer to the Appendix section on the last page for samples and required data 
format.
(3) Paste the Python server code listing text (must be text, not a screenshot graphic of the 
text) in the report. Use consolas font size 10 or equivalent monospace font. The use of 
the monospace font is to clearly show indentations in your code.
Page 16 of 19
Part 2c: UDP Pinger with Delays and Packet Losses 
Packet Loss Injection 
UDP provides applications an unreliable transport service. Messages may get lost in the network 
due to router queue overflows, faulty hardware, or some other reasons. Because packet loss is 
rare or even non-existent in typical campus or home networks, you are asked to modify the 
server code in this portion of the assignment to inject artificial losses to simulate the effects of 
network packet loss.
Hint: Create a variable which holds a randomized integer to determine whether a particular in coming packet is lost or not.
Part 2c Items To Submit 
Include Part 2c Python server code file xxP2c.py in the submission zip file.
In the PDF file report, Create a section called Part 2c – UDP Pinger with Delays and Packet Loss es. Include the followings:
(1) Describe the operation of your UDP Ping Server and explain how it simulates delays be tween 10ms and 20ms, with up to 10% packet losses.
(2) Explain how to run your code, i.e., command line and any applicable parameter(s)
a. Include run-time screen captures for a sequence consists of 50 pings
Refer to the Appendix section on the last page for samples and required data 
format.
(3) Paste the Python server code listing text (must be text, not a screenshot graphic of the 
text) in the report. Use consolas font size 10 or equivalent monospace font. The use of 
the monospace font is to clearly show indentations in your code.
 
Page 17 of 19
Appendix 
All examples in this section use an arbitrary student named Alice.
Part 2a: Sequence of 10 Pings with No Delay and No Packet Loss 
 
Alice 1: server reply: Alice 1 Fri Sep 13 09:00:15 2024, RTT = 3.99 ms
Alice 2: server reply: Alice 2 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Alice 3: server reply: Alice 3 Fri Sep 13 09:00:15 2024, RTT = 1.00 ms
Alice 4: server reply: Alice 4 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Alice 5: server reply: Alice 5 Fri Sep 13 09:00:15 2024, RTT = 1.01 ms
Alice 6: server reply: Alice 6 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Alice 7: server reply: Alice 7 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Alice 8: server reply: Alice 8 Fri Sep 13 09:00:15 2024, RTT = 1.00 ms
Alice 9: server reply: Alice 9 Fri Sep 13 09:00:15 2024, RTT = 0.00 ms
Alice 10: server reply: Alice 10 Fri Sep 13 09:00:15 2024, RTT = 0.99 ms
Min RTT = 0.00 ms
Max RTT = 3.99 ms
Avg RTT = 0.80 ms
Packet lost = 0.00 %
Page 18 of 19
Part 2b: Sequence of 10 Pings with 10ms-20ms Delays and No Packet Loss 
 
Alice 1: server reply: Alice 1 Fri Sep 13 09:57:59 2024, RTT = 20.76 ms
Alice 2: server reply: Alice 2 Fri Sep 13 09:57:59 2024, RTT = 16.00 ms
Alice 3: server reply: Alice 3 Fri Sep 13 09:57:59 2024, RTT = 16.00 ms
Alice 4: server reply: Alice 4 Fri Sep 13 09:57:59 2024, RTT = 15.88 ms
Alice 5: server reply: Alice 5 Fri Sep 13 09:57:59 2024, RTT = 15.02 ms
Alice 6: server reply: Alice 6 Fri Sep 13 09:57:59 2024, RTT = 15.18 ms
Alice 7: server reply: Alice 7 Fri Sep 13 09:57:59 2024, RTT = 15.29 ms
Alice 8: server reply: Alice 8 Fri Sep 13 09:57:59 2024, RTT = 15.42 ms
Alice 9: server reply: Alice 9 Fri Sep 13 09:57:59 2024, RTT = 15.67 ms
Alice 10: server reply: Alice 10 Fri Sep 13 09:57:59 2024, RTT = 15.74 ms
Min RTT = 15.02 ms
Max RTT = 20.76 ms
Avg RTT = 16.10 ms
Packet lost = 0.00 %
Page 19 of 19
Part 2c: Sequence of 50 Pings with 10ms-20ms Delays and up to 10% Packet Loss 
 
Alice 1: server reply: Alice 1 Fri Sep 13 09:45:50 2024, RTT = 12.01 ms
Alice 2: server reply: Alice 2 Fri Sep 13 09:45:50 2024, RTT = 16.00 ms
Alice 3: timed out, message was lost
Alice 4: server reply: Alice 4 Fri Sep 13 09:45:51 2024, RTT = 15.65 ms
Alice 5: server reply: Alice 5 Fri Sep 13 09:45:51 2024, RTT = 15.46 ms
Alice 6: server reply: Alice 6 Fri Sep 13 09:45:51 2024, RTT = 15.60 ms
Alice 7: server reply: Alice 7 Fri Sep 13 09:45:51 2024, RTT = 15.23 ms
Alice 8: server reply: Alice 8 Fri Sep 13 09:45:51 2024, RTT = 15.20 ms
Alice 9: server reply: Alice 9 Fri Sep 13 09:45:51 2024, RTT = 14.72 ms
Alice 10: server reply: Alice 10 Fri Sep 13 09:45:51 2024, RTT = 15.03 ms
Alice 11: server reply: Alice 11 Fri Sep 13 09:45:51 2024, RTT = 15.26 ms
Alice 12: server reply: Alice 12 Fri Sep 13 09:45:51 2024, RTT = 16.09 ms
Alice 13: server reply: Alice 13 Fri Sep 13 09:45:51 2024, RTT = 15.46 ms
Alice 14: server reply: Alice 14 Fri Sep 13 09:45:51 2024, RTT = 16.05 ms
Alice 15: server reply: Alice 15 Fri Sep 13 09:45:51 2024, RTT = 16.06 ms
Alice 16: server reply: Alice 16 Fri Sep 13 09:45:51 2024, RTT = 15.64 ms
Alice 17: server reply: Alice 17 Fri Sep 13 09:45:51 2024, RTT = 16.26 ms
Alice 18: server reply: Alice 18 Fri Sep 13 09:45:51 2024, RTT = 15.18 ms
Alice 19: server reply: Alice 19 Fri Sep 13 09:45:51 2024, RTT = 16.20 ms
Alice 20: server reply: Alice 20 Fri Sep 13 09:45:51 2024, RTT = 15.36 ms
Alice 21: server reply: Alice 21 Fri Sep 13 09:45:51 2024, RTT = 15.38 ms
Alice 22: server reply: Alice 22 Fri Sep 13 09:45:51 2024, RTT = 15.30 ms
Alice 23: server reply: Alice 23 Fri Sep 13 09:45:51 2024, RTT = 15.55 ms
Alice 24: server reply: Alice 24 Fri Sep 13 09:45:51 2024, RTT = 15.63 ms
Alice 25: timed out, message was lost
Alice 26: server reply: Alice 26 Fri Sep 13 09:45:52 2024, RTT = 15.99 ms
Alice 27: server reply: Alice 27 Fri Sep 13 09:45:52 2024, RTT = 14.50 ms
Alice 28: server reply: Alice 28 Fri Sep 13 09:45:52 2024, RTT = 15.27 ms
Alice 29: server reply: Alice 29 Fri Sep 13 09:45:52 2024, RTT = 15.18 ms
Alice 30: server reply: Alice 30 Fri Sep 13 09:45:52 2024, RTT = 14.89 ms
Alice 31: server reply: Alice 31 Fri Sep 13 09:45:52 2024, RTT = 15.47 ms
Alice 32: server reply: Alice 32 Fri Sep 13 09:45:52 2024, RTT = 15.80 ms
Alice 33: server reply: Alice 33 Fri Sep 13 09:45:53 2024, RTT = 15.19 ms
Alice 34: server reply: Alice 34 Fri Sep 13 09:45:53 2024, RTT = 14.99 ms
Alice 35: server reply: Alice 35 Fri Sep 13 09:45:53 2024, RTT = 15.21 ms
Alice 36: timed out, message was lost
Alice 37: server reply: Alice 37 Fri Sep 13 09:45:54 2024, RTT = 15.75 ms
Alice 38: server reply: Alice 38 Fri Sep 13 09:45:54 2024, RTT = 15.71 ms
Alice 39: server reply: Alice 39 Fri Sep 13 09:45:54 2024, RTT = 14.78 ms
Alice 40: server reply: Alice 40 Fri Sep 13 09:45:54 2024, RTT = 14.87 ms
Alice 41: server reply: Alice 41 Fri Sep 13 09:45:54 2024, RTT = 16.24 ms
Alice 42: server reply: Alice 42 Fri Sep 13 09:45:54 2024, RTT = 15.53 ms
Alice 43: server reply: Alice 43 Fri Sep 13 09:45:54 2024, RTT = 15.66 ms
Alice 44: server reply: Alice 44 Fri Sep 13 09:45:54 2024, RTT = 14.85 ms
Alice 45: server reply: Alice 45 Fri Sep 13 09:45:54 2024, RTT = 15.02 ms
Alice 46: server reply: Alice 46 Fri Sep 13 09:45:54 2024, RTT = 14.34 ms
Alice 47: server reply: Alice 47 Fri Sep 13 09:45:54 2024, RTT = 15.92 ms
Alice 48: server reply: Alice 48 Fri Sep 13 09:45:54 2024, RTT = 16.20 ms
Alice 49: server reply: Alice 49 Fri Sep 13 09:45:54 2024, RTT = 16.01 ms
Alice 50: server reply: Alice 50 Fri Sep 13 09:45:54 2024, RTT = 14.52 ms
Min RTT = 12.01 ms
Max RTT = 16.26 ms
Avg RTT = 15.37 ms
Packet lost = 6.00 %

 

访问网站(http协议)的最小分析 访问一个小网站的http抓包分析,旨在理解http的工作过程首先用思科模拟器中的服务器进行试验简单的拓扑图如下从PC0访问服务器(服务器自带http服务,且有默认网页,不需设置)从sniffer抓包(PC0->server)从sniffer抓包(server->PC0)经过前面简化的http访问分析,在心中对其中的数据来往有了一定的掌握,但还存在问题。为了解决上面的问题,下面在真实环境... 阅读详情

相关推荐

HTTP状态码大全 - 常用参考表对照表

HTTP状态码大全 - 常用参考表对照表

HTTP状态码详解

状态码 含义 100 客户端应当继续发送请求。这个临时响应是用来通知客户端它的部分请求已经被服务器接收,且仍未被拒绝。客户端应当继续发送请求的剩余部分,或者如果请求已经完成,忽略这个响应。服务器必须在请求完成后向客户端发送一个最终响应。 101 服务器已经理解了客户端的请求,并将通过Upgrade 消息头通知客户端采用不同的协议来完成这个请求。在发送完这个响应最后的空行后

Eliot 2600

Aspice的理解

ASPICE 是由汽车行业的主要公司和组织合作开发的,包括德国汽车工业联合会(VDA)和国际汽车工作组(Automotive SIG)。其目标是通过标准化的软件开发流程,提高汽车电子系统的软件质量和可靠性。

hkj8808的博客 2017

HTTP请求错误200、300、400、401、402、403、404、405、406、407、412、414、415、500、501、502解析

1开头的http状态码 表示临时响应并需要请求者继续执行操作的状态代码。 100 (继续) 请求者应当继续提出请求。 服务器返回此代码表示已收到请求的第一部分,正在等待其余部分。 101 (切换协议) 请求者已要求服务器切换协议,服务器已确认并准备切换。 2开头的http状态码 表示请求成功 200 成功处理了请求,一般情况下都是返回此状态码; 201 请求成功并且服务器创...

weixin_42595331的博客 1万+

Win7/Win8.1老系统求生指南:如何绕过KB2999226错误,成功安装VC++ 2015-2019运行库

本文详细解析了Win7/Win8.1系统安装VC++ 2015-2019运行库时遇到的KB2999226补丁缺失问题,提供了完整的补丁依赖链和分步安装指南。通过专业技巧帮助用户绕过常见错误,确保老系统能够兼容最新应用程序,提升工作效率。

weixin_32596893的博客 412

Win11家庭版如何让Win+R运行CMD默认管理员权限?3种方法实测有效

本文针对Win11家庭版用户,实测了三种让Win+R运行CMD默认获取管理员权限的有效方法。通过分析UAC机制与家庭版功能限制,详细介绍了注册表编辑、快捷方式创建与任务计划程序三种方案的原理、步骤与风险对比,帮助用户根据安全与效率需求选择最佳方案,实现一键高效管理。

sat99的博客 1283

【计算机基础】HTTP Status Code 状态码 大全

课程来自 https://www.imooc.com/learn/498 课程目录: 第1章 概述 第2章 Spring MVC拦截器的实现 2-1 拦截器工作原理 2-2 拦截器的实现 2-3 拦截器方法介绍 2-4 多个拦截器应用 2-5 拦截器的其他实现方式 第3章 拦截器的使用场景 3-1 拦截器的使用场景 第4章 拦截器与过滤器的对比及课程总结 4-1 拦截器与过滤器对比...

IN THE ZONE 3458

风机叶片小规模振动监测数据集--读取测试

ETH风电叶片缺陷数据集–读取测试 数据简介 提示:这里可以添加本文要记录的大概内容: 结构健康监测是保障重要机电设备、建筑设施健康的重要技术手段。 一、lvm_read包安装 示例:pandas 是基于NumPy 的一种工具,该工具是为了解决数据分析任务

cnjs1994的博客 2852

计算机网络:思科实验【8-运输层端口、TCP的运输连接管理、动态主机配置协议DHCP的作用】

推荐关注博主!随时获取更多关于计算机网路的最新技术分享!

m0_51574586的博客 2903

PS射击游戏射线检测优化:原理、工程与全链路高性能实现

射线池:减少GC,提升批量检测效率。分层检测:先粗后细,远距离射击高效判定。批量检测:并行处理,适合大量射线场景。空间结构:进一步加速大场景检测。下面继续深入射线检测优化,补充更多实用细节和进阶技巧,包括空间分区加速、射线检测多线程/异步化、射线合并与分帧、射线池通用模板、常见性能陷阱与调优建议等。对于极端性能需求,可自定义轻量级物理系统,仅检测关键对象(如玩家、子弹),跳过复杂物理引擎。结合AABB、OBB、球体等简单碰撞体,射线-包围体检测极快。空间分区+分层检测是大场景射线优化核心。

本博客聚焦游戏开发技巧、创业实战心得及大学热门课程干货。这里既有技术深度,也有思维广度,无论你是开发者、创业者还是高校学子,都能在这里找到适合自己的成长之路! 437

基于simulink的预测电流控制策略的三相逆变器仿真

本文详细介绍了在Simulink中实现基于预测电流控制策略的三相逆变器仿真方法。主要内容包括:准备工作(安装必要软件及工具箱)、构建三相逆变器基础模型、设计预测电流控制器(包含状态空间建模和控制器设计)、实现控制逻辑、添加示波器观察输出、配置仿真参数以及运行仿真分析结果。通过MATLAB代码示例和Simulink模块说明,展示了如何选择最优开关状态来最小化电流误差。该仿真方法为研究快速响应、高精度的逆变器控制提供了实用工具,但需注意实际应用中可能需要的调试工作。

amy_mhd的博客 278

HTTP从入门到精通

一 、基础概念 URL 请求和响应报文 二、HTTP 方法 GET HEAD POST PUT PATCH DELETE OPTIONS CONNECT TRACE 三、HTTP 状态码 1XX 信息 2XX 成功 3XX 重定向 4XX 客户端错误 5XX 服务器错误 四、HTTP 首部 通用首部字段 请求首部字段 响应首部字段 实体首部字段 五、具体应用 连接管理...

Umbrella Corporation 1万+

国科大学习资料--机器人智能控制_袁如意老师PPT后习题答案(学长精心整理)

人工神经元激活函数的作用是什么? 答:激活函数是用来加入非线性因素的,提高神经网络对模型的表达能力,解决线性模型所不能解决的问题。 人工神经网络的学习规则有哪些?各有何特征? 答:大类可以分为无监督学习算法、有监督学习算法和强化学习。其中无监督学习算法指只有输入信息,没有期望的输出信息,如Hebb学习规则,神经元连接强度的变化与两个相互连接的神经元的激活水平成正比。竞争学习法则:网络各输出单元相互竞争,最后达到只有一个最强者激活。有监督学习算法指同时提供输入信息和对应的期望输出信息,如误差学习(Delta学

无名何许人的博客 1488

471. Encode String with Shortest Length

471. Encode String with Shortest Length 题目链接:https://leetcode.com/problems... 这题还是有点难想的,一开始dp的思路想的还不对,参考这个博客的解释:http://www.cnblogs.com/grandy... dpi表示s[i, j]最短的压缩结果,subpr...

weixin_33978016的博客 198

PON架构(全光网络)

目前组网架构世界上有一种最快的速度又是光,以前传统以太网络规划满足不了现在的需求。有线网 无线网 全光网络方案场景 全光网络分类 以太全光网络 PON(Pas-sive-Optical Network 无源光网络) 再典型的中大型高校网络中 推荐万兆入室 千兆到桌面的带宽设计 一般三层 (终端-接入层-汇聚层-核心层-出口(安全设备)-互联网) 单校区核心设备 一般采用两台高性能的核心交换机 双机的方式采用的是 M-LAG 多校区之间核心交换机采用1

qq_56248592的博客 6272

ssm框架搭建

这个是一个在idea上成功跑起来的ssm框架项目,保存在这里方便以后使用直接下载

常用的Http Response Code状态码一览表

Response Code状态码一览表" title="常用的Http Response Code状态码一览表" height="507" width="470"> Response Code状态码一览表" title="常用的Http Response Code状态码一览表" height="627" width="471">

wangcg123的专栏 4118

android 蓝牙通讯demo

android 下蓝牙通讯demo,实现了发现蓝牙,使能蓝牙,通过蓝牙发送消息。

HTTP返回状态码及错误大全

http://www.kaiyuanba.cn/html/1/131/226/4258.htmHTTP 400 - 请求无效HTTP 401.1 - 未授权:登录失败HTTP 401.2 - 未授权:服务器配置问题导致登录失败HTTP 401.3 - ACL 禁止访问资源HTTP 401.4 - 未授权:授权被筛选器拒绝HTTP 401.5 - 未授权:ISAPI 或 CGI 授权失败...

weixin_30487317的博客 833

VC中sqlite的使用

在VC中对sqlite的使用,实现数据库大批数据的快速插入,读取数据库中的数据在ListCtrl中显示

Probability and Statistics - 4th edition

Probability and Statistics - 4th edition

常见HTTP状态码含义

对网站管理工作者来说有个词不陌生,HTTP状态码,它是用以表示网页服务器HTTP响应状态的3位数字代码。状态码的第一个数字代表了响应的五种状态之一。 1XX系列:指定客户端应相应的某些动作,代表请求已被接受,需要继续处理。由于 HTTP/1.0 协议中没有定义任何 1xx 状态码,所以除非在某些试验条件下,服务器禁止向此类客户端发送 1xx 响应。 2XX系列:代表请求已成功被服务器接收、理解、并...

线上幽灵 1743

http statusCode(状态码)

转自:1) http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3.html#unauthorized      2) http://openq.cn/http-statuscode-status-code-200300400500-sequence/ 完整版在这里: http://www.w3.or...

weixin_33795806的博客 442

http状态码---关于404和它的兄弟们

可能大家经常会见到404not found,无法找到指定位置的资源,其实404是http请求状态码的一种。 那么http状态码是什么呢?它是怎么产生的呢? 定义 每一个http响应都会带有一个http状态码用来表示http服务器的响应状态。 http所有状态码的第一个数字代表了响应的状态,1:消息,2:成功,3:重定向,4:请求错误,客户端有误,5、6:服务器错误。 产生 当浏览者访问...

weixin_44239385的博客 5485

常见Http状态码大全

一些常见的状态码为:200 - 服务器成功返回网页404 - 请求的网页不存在503 - 服务不可用详细分解:1xx(临时响应)表示临时响应并需要请求者继续执行操作的状态代码。代码 说明100 (继续) 请求者应当继续提出请求。服务器返回此代码表示已收到请求的第一部分,正在等待其余部分。 101 (切换协议) 请求者已要求服务器切换协议,服务器已确认并准备切换。2xx (成功)表示成功处理了请求的...

曲小强 1万+

HTTP协议状态码

100-199:服务器成功接收部分请求,要求客户端继续提交其余请求才能完成整个处理过程。 200-299:服务器成功接受请求,并已完成处理过程。 300-399:为完成请求,客户需要进一步细化请求。 400-499:客户端请求有错误。 500-599:服务器出现错误。 常用状态码: 200:OK请求成功。 301:所有请求页面已永久转移到新的URL。 302:所有请求页面已经临时转移到新的U...

HelloNing 294

HTTP协议的状态消息都有哪些?

状态码分类 已定义范围 分类 1XX 100-101 信息提示 2XX 200-206 成功 3XX 300-305 重定向 4XX 400-415 客户端错误 5XX 500-505 服务器错误

xiebiaoling的专栏 1748

学习C#开源报表组件Seal Report(45:报表服务安全配置)

学习Seal Server Manager软件内与报表服务安全配置相关的各类属性的用途

gc_2299的博客 161

Swift 字符详解:从 Character 到字符串遍历

Swift中Character代表扩展字形簇,符合人类对“一个字符”的直观理解。它与String为集合关系,可通过for-in遍历或数组拼接。Character基于Unicode,组合字符(如带重音字母、表情符号)视为整体,count统计字形簇数而非码点或字节。访问需用String.Index,不可直接整数下标。字符支持比较、大小写转换及ASCII互转,但必须用双引号声明,且与String类型区分。理解其设计可避免常见错误,提升字符串处理可靠性。

2402_85743155的博客 303

C# 系列教程_12 字符串 string 保姆级系统教程(面向新手,大量示例 + 原理讲解)

C#中string与String为同一类型,均为不可变引用类型,任何“修改”操作均返回新字符串。常用创建方式包括字面量、逐字字符串@""、插值$""及new String()。字符串本质是字符数组,支持索引访问但不可修改。所有方法如IndexOf、Substring、Replace等均不改变原字符串,返回新实例。

zhanghaha1314的博客 281
上一篇: AME 209/MSE 280 Matlab script
下一篇: Neural Networks for Image Classification
wx____codinghelp
博客等级 码龄2年 771粉丝 115原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值