What was the point of this?

Hiya there! Understanding how HTTP works behind the scenes is everything. I mean consider HTTP a platform where all the important actions are taken. Lets just say you've an app and a resource name stock. It lives on remote servers. And a user visits your website and requests your server to get him/her a catalogue of everything thats stored in the stock. So whenever he'll interact with the website and make a request for the catalogue, a request is generated in form of GET request. Also this request will contain some information like what catalogue is user requesting. Its called Payload. You can actually read the request object in DevTools if you're curious. Now the server makes the request to the framework/back-end which routes it to controller and controller takes the request and get the appropriate information from the models and send it back to the server. Which in turn gets rendered (it could be a HTML or XML or jSON) and user recieves a response of 200 OK, which means everything went well and response was successful. This is one request-response cycle. It all happens in HTTP. Consider httpbin.org the resource and *food=sandwich&drink=water * the payload.

~ Ari