Hypertext Transfer Protocol is an application layer protocol which is part of the TCP/IP family. That means that it’s a protocol for the ends of a transmission over TCP/IP. In a client-server relationship HTTP is the protocol for how the end client will communicate and pass information to the and from the end server. For example, web documents, including HTML, images, videos, etc. are passed individually through HTTP then constructed on the client into a single complete document to be presented as a website.
HTTP is passed through TCP or Transmission Control Protocol which is a transport-layer protocol that provides a connection based data transmission service. TCP is passed through IP or Internet Protocol which is a network layer protocol providing a connectionless data transmission service. The data is passed from link to link, there is no end-to-end connection established.
The protocol defines a set of request methods to tell the recipient what actions need to be performed. These request methods are referred to as HTTP Verbs. The REST architecture uses a particular subset of HTTP Verbs that correlate to CRUD (Create, Read, Update, Delete) operations. While REST only uses a handful of the verbs there are 39 total HTTP Verbs as of now.
This has been a very high level overview of the more common HTTP Verbs. Use the information here to help better your understanding of how Hypertext Transfer Protocol works. If you aren’t confined to a particular architecture (REST) by your framework, try out some of the less common ones that you may not have used before. This can be a starting point for more in depth learning on how the underlying processes we use as web developers work.