CS475: Computer Networks - HTTP Client (100 Points)

Assignment Goals

The goals of this assignment are:
  1. To implement a socket-based client

The Assignment

In this assignment, you will write an HTTP client.

HTTP Client

Using network sockets, write a program that accepts a command-line argument representing the web server to connect to. You can send an HTTP request to a given server over port 80 (you may use another command line argument for the port, if custom ports are desired). You should send the following over your socket:

GET /index.html HTTP/1.1\r\n
Host: www.google.com\r\n
\r\n

The following python program will get you started:

import socket

def connect(host, port, url):
    conn = socket.socket(socket.AF_INET, socket.SOCK_STREAM) # SOCK_STREAM is a TCP connection over AF_INET, which is IP: TCP/IP
    conn.connect((host, port))
    connstr = "GET " + url + " HTTP/1.1\r\n"
    conn.send(connstr.encode())
    hoststr = "Host: " + host + "\r\n"
    conn.send(hoststr.encode())
    conn.send("\r\n".encode()) # blank line
    
    return conn # so we can read the response later

Then, read the entire result and display it on the screen. To do this, you can read the result from the conn object as follows:

def read_response(conn):
    data = ""
    while True:
        chunk = conn.recv(1024)
        if not chunk: 
            break
        data += chunk.decode('utf-8', 'ignore')
        
    return data

Test your client by connecting to a known webserver and verify that you receive a response. Print out each header and value via data.split(), which returns an array of lines of text in the response. If len(line.strip()) == 0, you know you’ve reached a blank line. Until then, you can split the line on the : character to separate the key from the value of each line of the header. Print those separately, and then print the entire body when you have run out of header lines (in other words, after reaching the first blank line!).

Extra Credit (50%): HTTP Server

Similarly, write an HTTP server that listens on a port (non-administrators can’t listen on ports below 1024, so you might try port 8080 or something similar).

To do this, you will first listen on a web port, as follows:

def server(port):
    host = "0.0.0.0" # ourselves
    sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
    sock.bind((host, port))
    sock.listen()
    
    while True: # accept one connection after another; do new requests have to wait while we process each one?
        conn, addr = sock.accept()
        data = ""
        while True:
            chunk = conn.recv(1024)
            if not chunk:
                break
            data += chunk.decode('utf-8', 'ignore')
            
        # Process the request here

When you get a request, again read the headers. You can split the first line of the request by space, and you know that the second token will be the URL (see our HTTP request format above!). That’s going to be a file path on your computer. You can open that file, read it, and send back the response as a properly formatted HTTP response message.

To read a file in python, you can do the following:

f = open(filename, "r")
for line in f:
  print(line)

To send an HTTP response header HTTP/1.1 200 OK followed by a Content-Length header indicating the number of bytes in the file we read, followed by the file data itself, over a TCP connection, you can do this:

headers = "HTTP/1.1 200 OK\r\nContent-Length: " + str(len(response_data)) + "\r\n\r\n"
conn.sendall(headers)
conn.sendall(response_data)
conn.sendall("\r\n")

Test your server by running a web browser and accessing http://localhost:<your port number>. In addition, test your client against your server (run the server first, then run the client!).

Note: please terminate the server as soon as you are finished with it. We did not take action to secure this server and so it should not run on a computer that is connected to the Internet without a firewall blocking incoming connections! For example, it will happily read any file path on your computer given as the HTTP request URL. What might we do to prevent this?

Submission

In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:
  • If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
  • Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
  • Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
  • Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
  • Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).

Assignment Rubric

Description Pre-Emerging (< 50%) Beginning (50%) Progressing (85%) Proficient (100%)
Algorithm Implementation (60%) The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run The algorithm fails on the test inputs due to one or more minor issues The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case
Code Quality and Documentation (30%) Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide
Writeup and Submission (10%) An incomplete submission is provided The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) The program is submitted according to the directions with a minor omission or correction needed, and with at least superficial responses to the bolded questions throughout The program is submitted according to the directions, including a readme writeup describing the solution, and thoughtful answers to the bolded questions throughout

Please refer to the Style Guide for code quality examples and guidelines.