1
00:00:00,330 --> 00:00:05,250
So I guess from this lecture onwards, we are going to start with the H2B protocol, so the underlying

2
00:00:05,250 --> 00:00:11,100
protocol that Gatti's Web application traffic between the Web server and the client is known as the

3
00:00:11,100 --> 00:00:12,660
hypertext transfer protocol.

4
00:00:13,580 --> 00:00:19,490
You will talk about the issue to be one, not one, the most common implementation of protocol is defined

5
00:00:19,490 --> 00:00:27,980
in the OT F.C. 72, thirty seven to thirty seven, which is it applies to all the wars and defining

6
00:00:27,980 --> 00:00:30,140
all of the 26 16.

7
00:00:30,350 --> 00:00:40,100
So the latest was known as the HTP two was published in May 2015 and defined in IFC 75 five forty.

8
00:00:40,430 --> 00:00:49,070
So the first release, HTP 1.0 is now considered aborted and is not recommended as the Internet involved.

9
00:00:49,640 --> 00:00:55,820
New features were added in the subsequent release of this should be protocol in SCDP one, not one feature

10
00:00:55,840 --> 00:01:00,680
such as persistent connection, option, method and several improvements.

11
00:01:00,830 --> 00:01:06,740
In a way, SOTU supports gashing were added just to be basically a client server protocol.

12
00:01:07,010 --> 00:01:13,110
We're in the client or we can save web browser makes a request to the server and in return the server

13
00:01:13,110 --> 00:01:14,510
will respond to the request.

14
00:01:14,870 --> 00:01:22,070
So the response by the server, it's mostly in a formal estimate formatted pages HTP protocol by default,

15
00:01:22,070 --> 00:01:27,050
users post eighty, but the web server and the client can be configured to use different.

16
00:01:27,050 --> 00:01:29,140
But it depends upon the web browser.

17
00:01:29,390 --> 00:01:31,340
Oh sorry, web server and the client.

18
00:01:31,640 --> 00:01:39,830
So now what is odd F.C. So Odysseas of detailed technical document with simply describing Internet standards

19
00:01:39,830 --> 00:01:47,210
and protocol created by the Internet Engineering Task Force, which is also called I e the F, so the

20
00:01:47,210 --> 00:01:53,900
file was not the RFQ document becomes a standard that can be followed when implementing the protocols

21
00:01:53,900 --> 00:01:54,890
in your application.