Question 23 A client's browser sends an HTTP request to a website. The website responds with a handshake and sets up a TCP connection. The connection setup takes 2.1 ms, including the RTT. The browser then sends the request for the website's index file. The index file references 8 additional images, which are to be requested/downloaded by the client's browser. Assuming all other conditions are equal, how much longer would non-persistent HTTP take than persistent HTTP? (Give answer in milliseconds, without units, rounded to one decimal place. For an answer of 0.01005 seconds, you would enter "10.1" without the quotes.)

1. Johnny is a web application designer who is currently debating whether to use persistent or non-persistent HTTP requests for his application. Assuming a web page requires the transfer of 8 objects from the server to the client, please assist Johnny in making this decision by computing how long it would take to receive 8 objects at the client when Johnny is: A. Using persistent HTTP requests B. Using non-persistent HTTP requests Please assume the following: The transfer of an object from the server to the client including the TCP Acknowledgement (ACK) by the client to the server takes 0.01 seconds. 0 The TCP handshake process takes 0.02 seconds. The TCP teardown process takes negligible time and may be ignored. Hint: HTTP messages at the Application Layer are transmitted over the TCP protocol at the Transport Layer.

What is the purpose and functionality of the HTTP method?

Accomplish the following tasks involving SNORT rules: Add an appropriate rule options part to the following rule headeralert udp any any  any 53 Add an appropriate rule header to the following rule options part(msg:”possible HTTP GET request”; sid:xxxxx; rev:y;) Write a complete rule header and rule options to detect an FTP connection attempt. Explain what the following rule does.alert tcp $HOME_NET 21  any any (msg:"FTP failed login";content:"Login or password incorrect"; sid:xxxxx; rev:y;)

Primitives of transport service assume asymmetry between the two end points during connection establishment, one end (server) executes LISTEN while the other end (client) executes CONNECT. However, in peer to peer applications such file sharing systems, e.g. BitTorrent, all end points are peers. There is no server or client functionality. How can transport service primitives may be used to build such peer to peer applications?

SMTP (Simple Mail Transfer Protocol) is the standard protocol for transferring mail between hosts. A TCP connection is set up between a user agent and a server program. The server listens on TCP port 25 for incoming connection requests. The user end of the connection is on a TCP port number above 1023. You have defined the packet filter rule set shown in the table below. These rules permit and/or deny inbound and outbound traffic between the user agent and the mail server. Describe the purpose of each packet filter rule in the table.  Rule Direction Source Address Destination Address Protocol Destination Port Action A2 In External Internal TCP 25 Permit B2 Out Internal External TCP > 1023 Permit C2 Out Internal External TCP 25 Permit D2 In External Internal TCP > 1023 Permit E2 Either Any Any Any Any Deny

A single link between two hosts can be used to send more than one file. Please tell me when shipments can be cleared. Is there a set amount of time for one wait and some flexibility with the other?

Can you recommend the best HTTP version for my use case? Explain the function of each status code used in HTTP 2.0 response messages.

write a  Node/Express web server that supports routing via endpoint /cookie. Declare a variable named a and initialize it to 10 seconds.In the callback of route /cookie:Check to see if the browser sends a cookie named startIf cookie start received by the server, increment value in variable a by 2 seconds.Creates and sends a cookie that expires after the number of seconds specified in the variable a.The cookie is to be named startwith assigned value of 450.Import package cookie-parser for cookie handling

Suppose an HTTP client makes a first GET request to the gaia.cs.umass.edu web server for a base page that it has never before requested, which contains an embedded object, which causes the client to make a second GET request. A very short time later, the client then makes a third GET request - for the same base page, with that third GET request having an  If-Modified-Since field (as does the 4th GET request that the client makes for the embedded object).  Neither the base object nor the jpeg object has changed. How many round trip times (RTTs) are needed from when the client first makes the third GET request (i.e., when it requests the base object for the second time) to when the base page and the jpeg file are displayed a second time, assuming that: any time needed by the server to transmit the base file, or the jpeg file into the server's link is (each) equal to 1/2 RTT the time needed to transmit an HTTP GET into the client's link is zero? the time needed by the server to transmit…