In the end, headers are just little messages that web browsers and servers can pass back and forth to one another.
The recipient can do something with those messages or choose to ignore them, but they are powerful tools in the process of delivering content to your users.
The request/response cycle is complete!
Our long journey across cyberspace is complete... until the user interacts with the page. Many interactions will trigger another journey that follows the same basic path from the browser to our server and back again.
But what if instead of simply requesting to receive some data we want to request our server to change some data?
What do you think the request should do differently if it wants the server to do more than send a response.
Respond here with your answer in just a few sentences or bullet points: