Objective

• interpreting an incoming request,
• identifying and finding the requested resource,
• preparing the proper response (which may be an error message), and
• delivering the content (which could be either text or binary data).

Details

Your web server must:

• Listen on port 8534 by default. (You can make this configurable, if you like; but, 8534 needs to be the default.)
• Correctly serve text, html, pdf, and images (gif, png, and jpeg). You may support additional types if you like.
• You response headers must include Content-Type and Content-Length.
  • You may assume the content type from the file's extension.
  • You may hard-code the file extension to mime-type mapping.
  • If there is no file extension, or if the file extension not recognized, use "text/plain"
• Return a 404 error when appropriate. (The response should also include a brief HTML message describing the problem.)
• Return a 400 error message when appropriate. (The response should also include a brief HTML message describing the problem.)
• If the requested document is a directory:
  • Return index.html, if present.
  • Otherwise, return a simple directory listing (with links). Important: Your link to subdirectories must end with '/', otherwise, the web browser won't properly reset the base directory. (In other words, your href needs Images/ not just Images.)

Extra Credit

1. Make your server multi-threaded so that it can serve multiple requests at once.
2. Implement an HTTPS server. Warning: I hear that getting the certificates set up correctly can be challenging. I've never done this; so, if you run into trouble, I'll be of limited help.

Rules

• You may work on this assignment in teams of at most two.
• You may use any language you like. Realize, however, that I will be of limited help if you choose something other than Java. (I know C, C++, and Ruby well; but, I don't know much about the particular networking libraries. I do not know any .net languages. I do not know Windows well.)
• You may use standard socket and I/O libraries. You may not use any libraries that implement significant web server functionality (e.g., com.sun.net.httpserver).
• Cite any sources you consult. Avoid articles that provide complete (or nearly complete) solutions.
• Every file should begin with a comment that includes the names of all team members.
• Follow good design practices. In particular, break your code into methods to avoid code duplication and to keep methods from getting too long.

Submission and Grading

This project will be partially auto-graded using GitHub Classroom and TravisCI. Begin by using following this link to create a repository for this project. Once you have created your repository for this assignment, clone the repo to your local machine. Your repository will contain the following files:

MyStaticWebServer.java

This file contains some code to help you get started (including most of the code from the sample server we discussed in class). You don't have to use this file, or any of the code in it. But, if you choose a different file, you will have to adjust the Makefile accordingly so that autograder can build and run your server. (I'm happy to help you do this.)

Makefile

The autograder will use this file to build, run, and test your server. If you put all your code into MyStaticWebServer.java, you won't need to modify this makefile. However, if you have a different design in mind, go ahead. I'm happy to help you adjust the makefile as necessary.

.travis.yml

The autograder uses this file to configure the virtual machine used to run your tests. If you choose to write your server in a language other than Java, you may have to adjust this file. I'm happy to help you do that.

studentData

This directory contains files you can use to test your server. To launch your server with this directory as the root,

1. cd into this directory
2. Run java -cp .. MyStaticWebServer

testPlan.txt

Complete this document to specify how you will test your server.

secretTests.tar.end

This file will be added later. It contains an encrypted version of the tests I will use on your code. Attempting to decrypt or otherwise view these tests is a serious violation of the CIS Academic Honestey Policy..

Steps for completion and submission

1. Begin by writing your test cases. Look through the requirements above, and write a short paragraph describing how you will verify that your server meets each requirement. (testPlan.txt includes a couple samples.)
2. Write your code. Make sure your name appears in all files.
3. When your code passes all of your tests, push to the master branch. TravisCI will automatically run my tests.
4. If your code fails my tests:
   • Figure out what is missing from your test plan and add it.
   • Fix your code
   • Resubmit.
   Your test plan should indicate which tests were added in response to failing CI builds. (If you have many failing CI builds, but no additional tests cases, I'll know you didn't follow the testing procedure.)
5. When your code passes TravisCI, schedule a demo with me.

Hints and Reminders

• The URL for a directory should end with a '/', otherwise the relative links to the files won't work correctly. (See details above.)
• Remember to call close on your socket at the end of every call. Forgetting to close a socket may cause the next request to hang.
• If you want to commit code to the master branch without running the CI build, just add [ci skip] to the commit message.
• You must have a written test plan (described above). You will loose points for running the CI server without a reasonable test plan.
• This project will not be graded until it passes all of my tests. Your grade is based primarily on when you get all the automated tests passing. (Code design and testing will also factor into your grade.)
• There are two stages to passing the tests.
  1. First, your code must pass the automated tests in TravisCI
  2. Then, you must demonstrate your server to me and demonstrate that it can properly handle requests from a standard web browser
  It is your responsibility to schedule a demo time with me.
• Every file should include all team member names.

Updated Monday, 16 March 2020, 1:30 PM