# Request and response notes

## Checkpoint 1
Read the request and response shown on lines 1-32 of the lab. Choose 
five lines from the request and/or the response. For each, make an inference
about the meaning of the line, and some situation in which it might be useful. 
You are welcome to research the meanings of these headers, but it's also 
fine to speculate for now.


Line 12 is related to the connection type, it can be useful to know the connection went through and didn't fail
Line 13 has something to do with size of the file, this can be useful for how much space it takes up 
Line 14 is the coding language which is useful for the user to code into the files
Line 25 shows how many correct answers the users have guessed, this can be useful for assessing users on something or just collecting data
Line 28 is the ID of the riddle, this is helpful to edit the riddle or identify it when coding


## Checkpoint 2
The goal of this checkpoint is to see what status codes you can get back from 
the riddle server. Paste below several `http` requests and the status codes
they return.

http -v post https://riddles.makingwithcode.org/new question="What have I got in my pocket?" answer="My precious"
HTTP/1.1 200 OK

http -v get https://riddles.makingwithcode.org/new question="What have I got in my pocket?" answer="My precious"
HTTP/1.1 405 Method Not Allowed

http -v post https://riddles.makingwithcode.org/new question="What have I got in my pocket?" 
HTTP/1.1 400 Bad Request

http -v post https://riddles.makingwithcode.org question="What have I got in my pocket?" answer="My precious"
HTTP/1.1 404 Not Found