Assignment 0-5

Due Date: 2019-12-12

Available Points: 9 (Extra points)

HTTP design improvements, WARC file comparison, and in the wild examples of non-standard status codes, wrong MIME types, and unsafe methods.

Non-standard Status Codes

Find up to two “in the wild” examples of different response codes not defined in an RFC (e.g., 299 or 999)
Standard HTTP status codes and their corresponding RFCs are listed in the HTTP Status Code Registry
Post your findings in this thread

PATCH, PUT, and DELETE Methods

Find “in the wild” examples of domains that supports PATCH, PUT, or DELETE methods
You can find up to three examples from different domains, one for each method
Post your findings in this thread

Wrong API MIME Type

Find an “in the wild” examples of an API with a MIME type of application/json that should be something else and suggest what the MIME type should be
Post your finding in this thread

HTTP/1.1 Design Improvements

Provide up to two well-documented examples of what you would change in HTTP/1.1
Do not suggest features present in HTTP2 or proposed for HTTP3, rather some of the syntax and consistency issues we discussed in class (during the semester we covered several areas where HTTP/1.1 could have been designed more consistently)
Document both how things are in HTTP/1.1 and what you would propose instead
Post your proposals in this thread

WARC File Comparison

Compare and contrast the resulting WARC files on the https://odu.edu/compsci URI generated by any two of the following tools:
- Wget
- WARCreate
- Squidwarc
- Webrecorder
- WARCIO
- Heritrix
Post your analysis in this thread

Submission and Evaluation

Post your findings in their corresponding threads in the discussions repository
Include command-line output of cURL in plain text (screenshots are optional, but not sufficient)
The examples have to be different from those in the class slides and those already shared by others