1
00:00:00,480 --> 00:00:08,820
Hypertext Transfer Protocol HTTP is an application protocol, hypertext is basically structured text

2
00:00:08,970 --> 00:00:12,090
that uses logical links between nodes containing text.

3
00:00:13,120 --> 00:00:17,980
And HTTP is the protocol to exchange or transfer hypertext.

4
00:00:19,140 --> 00:00:28,410
So HTP is a stateless protocol that means no information is retained by other sender or receiver, it

5
00:00:28,410 --> 00:00:33,240
functions as a request response protocol in the client server computing model.

6
00:00:34,380 --> 00:00:40,230
A Web browser, for example, may be the client and an application running on a computer that's hosting

7
00:00:40,230 --> 00:00:41,820
a Web site, maybe the server.

8
00:00:43,050 --> 00:00:47,070
The client submitted HTP request message to the server.

9
00:00:48,010 --> 00:00:55,870
The server, which provides resources such as HTML files and other content, returns a message to the

10
00:00:55,870 --> 00:00:56,230
client.

11
00:00:57,390 --> 00:01:03,510
The response contains completion status information about the request and may also contain requested

12
00:01:03,510 --> 00:01:05,370
content in its message body.

13
00:01:06,310 --> 00:01:10,930
So the most used HTTP request is get.

14
00:01:11,950 --> 00:01:15,780
A get request is designed to request server resources.

15
00:01:16,810 --> 00:01:22,180
With this type of request, the parameters are sent to the server inside the euro.

16
00:01:23,850 --> 00:01:31,590
A post request is designed to request server resources as well as a get request, unlike aget request,

17
00:01:32,010 --> 00:01:37,560
parameters are sent to the server inside the body of the request instead of the euro.

18
00:01:38,800 --> 00:01:44,470
Well, you know, it's still possible to send the parameters inside the URL, but if you use a post

19
00:01:44,470 --> 00:01:50,380
request, it's better to send parameters inside the body than inside the URL.

20
00:01:51,650 --> 00:01:55,640
So what's the advantage of sending parameters inside the body instead of the URL?

21
00:01:56,930 --> 00:02:02,210
Almost always the traffic between the server and the client is logged on the server side.

22
00:02:03,140 --> 00:02:05,840
Such log files usually contain the URL.

23
00:02:06,880 --> 00:02:14,860
If you send the parameters in the URL, they are saved as clear text in your log files so anyone who

24
00:02:14,860 --> 00:02:22,000
can see the log files can also see your sensitive parameters, you should use post request to send sensitive

25
00:02:22,000 --> 00:02:22,360
data.

26
00:02:24,000 --> 00:02:30,270
But please note that it's not enough for the privacy of the traffic because any man in the middle who

27
00:02:30,270 --> 00:02:35,850
listens to the network will see the parameters, even though they are inside the body of the request

28
00:02:35,850 --> 00:02:36,330
message.

29
00:02:37,110 --> 00:02:41,340
So you should encrypt your traffic always.

30
00:02:43,070 --> 00:02:48,680
Now, the server, which provides resources such as HTML files and other content, returns a response

31
00:02:48,680 --> 00:02:49,910
message to the client.

32
00:02:51,100 --> 00:02:57,430
The response contains completion status information about the request and may also contain requested

33
00:02:57,430 --> 00:02:59,080
content in its message by.

34
00:03:00,220 --> 00:03:08,910
So every response has a three digit response status code, such as 200, OK, 302 found, et cetera.