# 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 1 - GET /all HTTP/1.1 is the request line. This line is useful because when a web browser loads a page, it uses GET to ask the server to send back the content.

Line 5 - riddles.makingwithcode.org: tells the server which website/dpomain the cllient wants to talk to. This line is useful because it helps the server know which website to serve when multiple sites are running on the same IP address.

Line 6 - User-Agent: HTTPie/3.2.4: identifies the program or browser that is making the request so this one is the http. This is useful because websites can serve different content or block certain bots based on what is requesting on the page such as mobile device vs desktop.

Line 7 - HTTP/1.1 200 OK: Status line in response - OK meaning the request was successful and the server is sending back the date we asked for. This is useful for when websites/pages do not load correctly or something went wrong. 

Line 10 - Content - Type: applicatin/json: Tells the client what format the response body is in - this case JSON data (a structured way to send information). This is useful as it allows programs/apps to now how to parse the data - website knows it should be a JSON rather than HTML or image. 

## 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.

Testing code