•   To understand client-server communication via sockets.
   
•   To gain exposure to the basic operations of a Web server and client.
   
•   To explore basic structures of HTTP messages.
   

Due: April 14, 2020 11:59pm Project Description 

In this project, you will be developing a multithreaded Web server and a simple web client. The Web server and Web client communicate using a text-based protocol called HTTP (Hypertext Transfer Protocol). 

Requirements for the Web server 

•   The server is able to handle multiple requests concurrently. This means the implementation is multithreaded. In the main thread, the server listens to a specified port, e.g., 8080. Upon receiving an HTTP request, the server sets up a TCP connection to the requesting client and serves the request in a separate thread. After sending the response back to the client, it closes the connection.
   
•   The server is assumed to work with HTTP GET messages. If the requested file exists, the server responds with “HTTP/1.1 200 OK” together with the requested page to the client, otherwise it sends a corresponding error message, e.g., “HTTP/1.1 404 Not Found” or “HTTP/1.1 400 Bad Request”.
   
•   If running the server program using command line, the syntax should be: server_code_name [<port_number>]
  where the optional <port_number> is the port on which the server is listening to connections from
  clients. If the port number is not entered, the default port 8080 is used.
   
•   You can test your Web server implementation on your local machine using a Web browser, e.g.,
  Internet Explorer, Firefox, or Chrome. You need to specify the used port number within the URL, for example,
  http://localhost:8080/index.htm
  If omitting the port number portion, i.e., 8080, the browser will use the default port 80.
   
•   The server should response with a default page when users do not enter a specific page in the URL,
  for example,
  http://localhost:8080/
  It should also work when the request includes a path to the requested file, for example,
  http://localhost:8080/path/to/file/example.htm
   
•   You should display/log the request and header lines of request messages on the server for the purpose of debugging.
  Requirements for the simple Web client
   
  •   The client is able to connect to the server via a socket and to request a page on the server.
     
  •   Upon receipt of the response message from the server, the client extracts and displays/logs the
    message status, and then retrieves the page content from the message body.
     

 If running the client program using command line, the syntax should be:
client_code_name <server_IPaddress/name> [<port_number>] [<requested_file_name>] 

where the <server_IPaddress/name> is the IP address or name of the Web server, e.g., 127.0.0.1 or localhost for the server running on the local machine. The optional <port_number> is the port on which the server is listening to connections from clients. If the port number is not entered, the default port 8080 is used. The optional <requested_file_name> is the name of the requested file, which may include the path to the file. If the file name is not entered, the default file “index.htm” is used. 

Notes: 

•   This is an individual project.
   
•   You can use the programming language of your choice. (You may get more help with Java or Python.)
   
•   You may use the skeleton code for the server provided in the textbook’s companion website for reference. You may also want to refer to the textbook, chapter 2, section 2.2.3, for more details on HTTP message format and section 2.7, for socket programming.
   
•   The source codes should be well documented to make it easier for the TA to follow.
  Submission Guidelines
   
  •   Submit a single zipped file with the naming convention <your_UTA_id>_<your_name>.zip which consists of:
     Source codes of the Web server and client,
     Any additional files required to run your codes,
     A readme file with instructions on how to compile and run your codes. You must mention the IDE as well as any packages that are required to run the codes.
     
  •   Do NOT include any runnable executable (binary) program.
     
  •   Make sure your name and your SAU ID are also listed in the readme file and in comments at the
    beginning of your source files.
     
  •   Upload the zipped file via Canvas. Please strictly follow the naming convention of the zipped file and the subject title.
     
  •   Late submission will be accepted with a 10-point deduction for each extra day.
    Additional Requirements/Instructions
     
    •   Complete documentation and instructions for running the codes are recommended, otherwise you may be asked to come give the TA a demo if he is not able to run your programs from the instructions provided.
       
    •   If you are using any code from some external source or book, you MUST mention it explicitly in the codes as well as the readme file. Otherwise, it will be considered plagiarism and your project will not be evaluated.
       
    •   You can discuss with other classmates on steps/algorithms to implement the project. However, the source codes must be written yourself.