Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

I will Rate LifeSaver for easy to understand correct answers to this that I can

ID: 3637330 • Letter: I

Question

I will Rate LifeSaver for easy to understand correct answers to this that I can use to write my paper. Not asking for someone to write the paper just help get me going. Thank you for your time.

Telnet is a long-time favorite for troubleshooting connection issues. It can be used to attempt to connect to a server on a given port. Generally you can quickly confirm that you can get to the remote server from your test box, and that a server is running and bound to the specified port you requested.

More specifically, Telnet can be used to test HTTP scenarios, effectively stripping through all the friendly layers a browser usually hides from web visitor eyes. Troubleshooting HTTP using telnet is a great way to review exactly what is getting returned to your browser during a Web request for a particular URL. This allows you to see headers and collect other information related to the Web server.

For this assignment, you will make some HTTP 1.1 requests using Telnet. You can either use the Windows command prompt, or something more user friendly like CYGWIN or Putty (note that installing CYGWIN can take quite a while, only recommended to those who have previous experience with it). Start the Telnet client and connect to port 80 of the server for “example.com” by typing in the command window

>telnet example.com 80

Note: this launches telnet and tells it to look up and connect to the server for "example.com" on port 80. At this point, the connection is open so you just get a blank line waiting for input. You can now enter your HTTP request, followed by two <enter> keystrokes, if you use the Windows command lines.

Try GET and POST requests, and see what responses come back from the server. Write a paper explaining your HTTP requests and the server responses.

The response I keep getting is:
HTTP/1.0 302 Found
Location: http://www.iana.org/domains/example/
Server: BigIP
Connection: Keep-Alive
Content-Length: 0

or same as above except for Connection: close , when I try a post.

Explanation / Answer

your "GET" request is the same thing that a browser will send when requesting a page. The response you are getting there tells what version of HTTP the page is using (1.0), as well as what can be understood as a command being sent back to the browser. 302 Found means that the page was found, but is a redirection. If you have ever seen a 404 Page Not Found error, it's the same kind of HTTP response. If it were a browser being used it would receive that 302 and then send another GET request to the location listed, http://www.iana.org/domains/example/. You can test this by going to www.example.com in your browser which will then forward you to the other page. The connection keep-alive signifies that even though it is transferring you, it is leaving the connection to that server open for the time being. Finally, content-length displays how many bytes of actual page information was transferred. In this case, there is no actual content being sent, so it's 0. Hope this was useful.