comp2406 Assignment 2

In this assignment you will be be extending the functionality of tinywebserver.js from Tutorial 2. There are 10 points. This assignment is due on January 31, 2016 (extended from January 28th).Please submit your answers as a single text (javascript) file called "tinyweb.js". Please cite any sources you used in creating your answer as comments in your code.Your tinyweb.js (a modified version of tinywebserver.js) should have the following functionality:
  1. [1] Add a new 777 status code if there is a request for any document with the word "lucky" in its URL (path or document name).
  2. [1] Add a command line argument which is the name of a configuration file. This file should contain the contents of the options object. Note that tinyweb.js should start up correctly without this option file being specified; in this case it should behave as tinywebserver.js does (with respect to the options, not the lucky return code).
  3. In the configuration file add the following properties to the option object that change the behavior of the app as follows (note it should also contain all the options that were already part of the options object):
    • [2] logged-headers: an array of headers (as strings) that should be logged for each incoming request. If no logged headers are specified, no headers should be logged. Header names should be in all lowercase with words separated by dashes. Thus "UserAgent" becomes "user-agent". (This change is because this is the format of header names in request.headers.) The format should be three spaces, the header name, a colon, a space, then the contents of the header.
    • [2] logfile: the filename where to write log messages. They should be written to standard out (as console.log does) if no logfile is specified.
    • [2] errorpage: html file to be returned when an error page is returned (not 200). The 777 status code should NOT return an error page, it should return the regular document (777 is an alias for 200).
    • [2] aliases: object where the key is the alias and the value is what should be substituted. The alias should be for the entire doc path (the URL without the hostname). Aliases should be handled before lucky URL processing (and really, just about everything else).
  4. Hintslog filesTo log everything to a file you'll want to use a custom Console object with a special write stream. To get append-only behavior (as logs shouldn't normally be erased) do something like this:
    1. // logdemo.js
    2. // invoke as:
    3. // node logdemo.js <logfile
    5. var fs = require("fs");
    6. var Console = require('console').Console;
    7. var logFilename = process.argv[2];
    8. var logStream;
    10. // Note: this doesn't catch all errors, see
    11. //
    13. try {
    14. logStream = fs.createWriteStream(logFilename, {'flags': 'a'});
    15. } catch(e) {
    16. logStream = process.stdout;
    17. }
    19. var myConsole = new Console(logStream);
    21. myConsole.log("This will be written to a file, unless there was a problem!");
    JSON parsingJSON.parse() is very strict with its parsing, much stricter than regular object declarations in JavaScript. In particular properties need to be quoted (only with double quotes). You can use try/catch to allow this to be handled gracefully:
    1. try {
    2. options = JSON.parse(fs.readFileSync(optionsFilename, "utf-8"));
    3. } catch (e) {
    4. if (optionsFilename) {
    5. console.error("Error reading/parsing options file " + optionsFilename +
    6. ", using defaults.");
    7. } else {
    8. console.log("No options file specified, using defaults.");
    9. }
    10. options = default_options;
    11. }
    example configHere's as example config file:
    1. {
    2. "host": "localhost",
    3. "port": 8000,
    4. "index": "index.html",
    5. "docroot": ".",
    6. "logged-headers": ["user-agent", "referer"],
    7. "logfile": "tinyweb.log",
    8. "errorpage": "error.html",
    9. "aliases": {
    10. "/index.html": "/hello.html",
    11. "/": "/hello.html",
    12. "/really/cool.html": "/notcool.html"
    13. }
    14. }
    example header logHere's an example of the header log messages:404 POST /useName
    user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.82 Safari/537.36
    referer: http://localhost:8000/formtest.html
Powered by