Use Wireshark to answer the following question:

Q1: What is the HTTP response code sent by the server after the first request?

Q2: By looking at the captured traces, which of the following explanations applies to the observed behaviour in the browser?

Select one:

a. The txt file is hosted at the bit.ly server, and is server directly to the client.

b. The client browser connects to a DNS server to resolve the bit.ly address name into the real hostname

c. The server form bit.ly acts as a proxy, sending a request to the ieft server, retrieving the txt file, and transparently returning the file to the client.

d. The server response code informs the browser that the file is available at a different location, thus triggering a second request from the browser to the right server.

Now we will use Wireshark to discover what happens at the protocol level when we use a URL shortener service such as bit.ly . These web applications have become very popular mostly to squeeze as much information as possible from limited size messages such as tweets. In this par we will be capturing the traffic originated from our browser to remote servers when we click one shortened URL. - Restart packet capturing with Wireshark. - In your web browser, enter the following URL (if you are repeating this experiment, you should clear the browser cache before going through the URL) https://bit.ly/33f5gKu - You should see a text document opening in your browser. Stop Wireshark capture now. It appears the browser has automatically decoded the shortened URL into the one it was ultimately pointing at