So I guess from this lecture onwards, we are going to start with the H2B protocol, so the underlying
protocol that Gatti's Web application traffic between the Web server and the client is known as the
hypertext transfer protocol.
You will talk about the issue to be one, not one, the most common implementation of protocol is defined
in the OT F.C. 72, thirty seven to thirty seven, which is it applies to all the wars and defining
all of the 26 16.
So the latest was known as the HTP two was published in May 2015 and defined in IFC 75 five forty.
So the first release, HTP 1.0 is now considered aborted and is not recommended as the Internet involved.
New features were added in the subsequent release of this should be protocol in SCDP one, not one feature
such as persistent connection, option, method and several improvements.
In a way, SOTU supports gashing were added just to be basically a client server protocol.
We're in the client or we can save web browser makes a request to the server and in return the server
will respond to the request.
So the response by the server, it's mostly in a formal estimate formatted pages HTP protocol by default,
users post eighty, but the web server and the client can be configured to use different.
But it depends upon the web browser.
Oh sorry, web server and the client.
So now what is odd F.C. So Odysseas of detailed technical document with simply describing Internet standards
and protocol created by the Internet Engineering Task Force, which is also called I e the F, so the
file was not the RFQ document becomes a standard that can be followed when implementing the protocols
in your application.