1
00:00:00,510 --> 00:00:08,790
‫Hypertext transfer protocol HTTP is an application protocol, hypertext is basically structured text

2
00:00:09,000 --> 00:00:12,090
‫that uses logical links between nodes containing text.

3
00:00:13,150 --> 00:00:17,950
‫And HTTP is the protocol to exchange or transfer hypertext.

4
00:00:19,140 --> 00:00:27,600
‫So HTP is a stateless protocol that means no information is retained by other sender or receiver.

5
00:00:28,140 --> 00:00:33,210
‫It functions as a request response protocol in the client server computing model.

6
00:00:34,410 --> 00:00:39,780
‫A Web browser, for example, may maybe the client and an application running on a computer that is

7
00:00:39,780 --> 00:00:40,850
‫hosting a website.

8
00:00:40,860 --> 00:00:41,820
‫Maybe the server.

9
00:00:43,080 --> 00:00:47,070
‫A client submits an HTTP request message to the server.

10
00:00:48,040 --> 00:00:55,390
‫The server, which provides resources such as HD, HTML files and other content, returns a message

11
00:00:55,540 --> 00:00:56,190
‫to the client.

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

13
00:01:03,480 --> 00:01:05,340
‫content in its message body.

14
00:01:06,340 --> 00:01:10,930
‫So the most used HD http request is get.

15
00:01:11,890 --> 00:01:15,750
‫A get request is designed to request server resources.

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

17
00:01:23,910 --> 00:01:29,310
‫A post request is designed to request server resources, as well as a get request.

18
00:01:30,030 --> 00:01:37,230
‫Unlike a get request, parameters are sent to the server inside the body of the request instead of the

19
00:01:37,260 --> 00:01:37,560
‫URL.

20
00:01:38,830 --> 00:01:44,440
‫Well, you know, it's still possible to send the parameters inside the URL, but if you use a post

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

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

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

24
00:02:03,170 --> 00:02:05,840
‫Such log files usually contain the URL.

25
00:02:06,880 --> 00:02:12,580
‫If you send the parameters in the URL, they are saved as clear text in your log files.

26
00:02:12,940 --> 00:02:18,790
‫So anyone who can see the log files can also see your sensitive parameters.

27
00:02:19,600 --> 00:02:22,360
‫You should use post request to send sensitive data.

28
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

29
00:02:30,270 --> 00:02:36,330
‫listens to the network will see the parameters even though they are inside the body of the request message.

30
00:02:37,110 --> 00:02:41,310
‫So you should encrypt your traffic always.

31
00:02:43,070 --> 00:02:48,650
‫Now, the server, which provides resources such as HD e-mail files and other content, returns a response

32
00:02:48,650 --> 00:02:49,880
‫message to the client.

33
00:02:51,130 --> 00:02:57,400
‫The response contains completion status information about the request and may also contain requested

34
00:02:57,400 --> 00:02:59,080
‫content in its message body.

35
00:03:00,220 --> 00:03:08,890
‫So every response has a three digit response status quo, such as 200, OK, 3.2 found, et cetera.