728x90
Appointments are the most important thing on the web. Because the web itself is communication. There was a time when all communication had to be conducted face-to-face. There was a time when it developed a little bit and communicated with it by writing text, and there was an era when it was actively communicating using computers and the web in a non-face-to-face state beyond face-to-face and text. The Web is the most efficient form of communication that has come to this day. This is because people around the world can connect and communicate with each other in real-time on the web and the Internet. Communication presupposes promise (you can call it "protocol" in computer terms) Let's imagine What happens if you try to communicate with each other without any promises in common? This would be similar to trying to communicate with cannibals in tropical forests or with different animals in zoos. Or at least like trying to talk to a foreigner who can't communicate at all.
People are flexible and flexible, so they can adapt quickly. For example, when you talk to a foreigner who can't communicate at all, you can try body language if you can't communicate too much. In "Greek Zorba," there's a story like that. However, what we use for web communication is a regular computer, not a person. Computers are machinesl. There's no human flexibility.
The web can be divided into three tiers: the presentation layer, transaction layer, and data layer. The presentation layer is the part of the web that users watch. This includes web screens that we see daily, such as HTML, css, and JavaScript. The transaction layer is primarily responsible for managing and handling data in the middle of both. User input goes through the transaction layer to the data layer. The data layer is, more simply, the database and its management.
HTTP stands for Hyper Text Transfer Protocol. As you can see from this acronym, it's a data exchange protocol. It's a protocol that determines how the data exchange of requests and responses is organized. In other words, HTTP itself promised the client's request and the server's response. 'Client-side requests and server-side responses' is an accurate representation of the core of the web.
간단한 예시를 볼까요?
요청 예시
POST/index.html HTTP/1.1
Host: navaasgda.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0 Safari/25.162
Accept: text/html,application/xhtml+xml,application/xml;q=0.9
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://243.12.47.3463/noll/dskjsf
응답 예시
HTTP/1.1 200 OK
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 123
Connection: Keep-Alive
Content-Type: text/html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="style.css">
<title>answers</title>
</head>
<body>
<h1 id=“hi”>Git on</h1>
<script src="script.js"></script>
</body>
</html>
728x90
'호그와트' 카테고리의 다른 글
| pseudo code (0) | 2022.11.11 |
|---|---|
| 웹 기본 2 (0) | 2022.11.10 |
| 자유자재로 응용하는 익스플로잇 (0) | 2022.11.10 |
| 쿠키와 세션 (0) | 2022.11.10 |
| 이상한 컴퓨터 과학 (0) | 2022.11.10 |