Do the following exercises.

• Use Express, as described here: Basic routing, to implement the following:

  • Routes — Implement all routes using this URL: localhost:3000/request.
  • Request Methods — Implement these methods: GET; HEAD; PUT; POST; DELETE.
  • Response Codes — Implement the appropriate HTTP response codes for the specified routes. For all unspecified routes return something appropriate other than Express’s default 404 not-found response. You can use the http-status-codes NPM module to define the return codes and the Express command my_application.all() to set/return them.
  • Data — Display the sample data that comes with those methods that support data.

• Demonstrate that your server can handle the requests, including the passage of data to the methods that support data. Do this, if possible, using both of these tools:

  • Chrome — Do what you can with the standard browser. Make sure that you can use Chrome Developer Tools to find the full requests and responses.
  • Curl — Curl is a command-line-based, Internet access tool. Its manual is rather dense, so here’s a quick reference for some commands that you’ll find useful.

    curl [--head] URL

    GET the specified URL; the head option gets only the header.

    curl -X method URL -d data -H 'Content-Type: application/json'

    Send the specified HTTP method/data to the specified URL. Here, the data is declared to be in JSON format, e.g., '{"arg":"value"}'.
    You can use the NPM body-parser to parse JSON data on the server side; see the sample code for an example of how to do this.

    Record which tool (Chrome and/or curl) could be used for each of the HTTP methods. Also record the Curl commands you used successfully (include them in the lab text file below).

When that is done, consider the following questions.

1. Identify the request methods that you can and can’t test using the two tools listed above. If a method cannot be testing using a particular tool, explain why this is the case. List the Curl commands you used successfully.
2. What is the most appropriate HTTP response code for pages that aren’t defined by an Express route?

Save your answers to these questions in a lab06.txt file in the root of your lab repo.

Work through the tutorial specified here: My first HTML form. Note the following.

• Add the form definition files (HTML and CSS) as static data for the server you implemented in exercise 6.1 under a public/forms sub-directory.
• Add the POST URL specified in the tutorial to the routes already defined in your server, but run the both (static) form and its posted result through the /forms route.
• Make sure that you can find the posted form data using Chrome Developer Tools.
• Include the form data in the webpage returned by your server. For details on how to do this, see the class example (references: the Express API for Request and the NPM body-parser module).

When that is done, consider the following questions.

1. What HTTP methods do forms support?
2. How is the form data being passed back to the server and what syntactic form does it take? Is the data modified in any way?

Save your answers to these questions in your lab06.txt file.