Exploring the request-response mechanism in HTTP – how clients and servers communicate
One of the great accomplishments of the 1980s, besides CFC-laden hairspray, was the development of a universal set of networking protocols known as TCP/IP. In case you are new to this, the correct way to pronounce this is as letters: tea sea pea eye pea. The slash is silent, just like it is with ninjas.
It took a while for it to be universally adopted, but ultimately it was, and the protocols of TCP/IP form the basis of the modern web. While there are many useful protocols serving a myriad of functions, I want to focus your attention on the Hypertext Transfer Protocol (HTTP). You can go ahead and include the secure counterpart, HTTPS, where the S stands for secure. They effectively work the same way, except that HTTPS is encrypted.
The request-response mechanism entails a chain of events that describes a conversation that happens between the web browser or client, and the web server...
