In March 1983, HTTP was born. The main purpose is to allow scholars in two places to share knowledge.

In 1990, it successfully developed the world’s first Web server and web browser.

In 1990, the HTML 1.0 draft was discussed and abandoned due to several ambiguities.

In January 1993, the ancestors of modern browsers developed Mosaic, which displayed HTML in inline and other forms.

In December 1994, Netscape Communications released Netscape Navigator 1.0.

In 1995, Microsoft released Internet Explorer1.0 and 2.0.

It was followed by Apache, which is now one of the server standards.

In 1995, when Microsoft and Netscape had a browser war, they each made extensions to HTML that required compatibility in some HTML.

Around 2000, Netscape was in decline.

The second browser war broke out in 2004 when the Mozilla Foundation released Firefox.

It took five years for Internet Explorer to go from 6 to 7. It was followed by 8, 9, and 10. Chrome, Opera, Safari, and other browsers have taken over the market.

HTTP came out in 1990, and at that time no formal standard was established.

In May 1996, HTTP was officially published as a standard.

In January 1997, HTTP 1.1 was announced.

HTTP is a subset of the TCP/IP protocol family.

The rules that allow different devices and operating systems to communicate are called protocols.

A collection of protocols associated with the Internet like this is collectively called TCP/IP.

TCP/IP consists of the application layer, network layer, transport layer, and link layer.

IP is different from AN IP address. IP is the name of a protocol at the network layer.

The IP address indicates the IP address assigned to the node, and the MAC address indicates the fixed IP address of the nic. An IP address can be paired with a MAC address. The IP address is changeable, but the MAC address remains unchanged.

The communication between IP addresses depends on THE MAC address. The communication parties usually pass through multiple computers and network devices to connect to each other. During the transfer process, the MAC address of the transfer device at the next station is used to search for the next technical secondary target. ARP is a protocol used to resolve addresses. The MAC address (physical address) of the communication party can be traced based on the IP address of the communication party.

The TCP byte stream service divides large chunks of data into packet segments for convenient transmission and manages them. TCP verifies whether data is finally sent to the peer. TCP is at the transport layer.

TCP uses a three-way handshake to ensure accurate delivery of data. A three-way handshake is marked by SYN (Synchronize) and ACK (Acknowledgement). In addition to the three-way handshake, TCP has other methods to ensure reliable communication.

The DNS service, like HTTP, is located at the application layer and provides resolution between domain names and IP addresses. You can search for an IP address by domain name or reverse search for a domain name from an IP address.

HTTP request simple flow:

  • Resolve a domain name into an IP address using DNS
  • Generates a server request packet through HTTP
  • This section describes how to use TCP to divide HTTP request packets into packet segments by sequence number and send the packet segments to the peer party
  • The IP protocol searches for the address of the other party and transmits it as it goes along.
  • The server reorganizes the received packet segments by sequence number through TCP
  • HTTP parses the request content
  • Successful completion of the request
  • The server returns the processing result over TCP/IP

URI: Unified Resource Identifier URL: Unified resource locator

A URL is an address that must be entered to access a Web page using a Web browser.

Uniform URIs refer to Uniform formats, making it easier to handle multiple types of resources, and making it easier to create new protocol methods. Resource is a Resource, anything that can be represented. Files, images, services, etc. can be distinguished from other types, either singly or collectively. Identifier is the Identifier. In general, a URI is a locator identifier for a resource represented by a protocol scheme. Protocol method indicates the name of the protocol type used to access resources. If HTTP is used, the protocol scheme is HTTP.

There are about 30 standard URI protocol schemes. Administered by IANA.

A URI is a string representing an Internet resource, and a URL is the location of the resource. Therefore, URL is a subset of URI.

URI format: user: [email protected]: 80 / dir/index. H…

  • HTTP: indicates the protocol scheme name
  • User :pass Login information (authentication)
  • www.example.jp Server address
  • 80 the port number
  • Dir /index.html Hierarchical file path
  • Uri =1 Query character string
  • Ch1 fragment identifier

Login information: It is optional to specify the username and password as required login information to obtain resources from the server.

Server address: The address can be a domain name, IPv4 or IPv6

Port number: Specifies the network port number connected to the server. If this parameter is omitted, the default port number is used automatically.

Hierarchical file path: Specifies the file path on the server to locate the specified resource.

Query string: Optionally, you can use the query string to pass in any parameter for the specified resource.

Fragment identifier: Identifies the child resources in the acquired resource, optional.

The documents that specify the technical standards for the HTTP protocol, called RFCS (Request for Comments), are usually followed by applications. The RFC is the design document for the Internet, and if it is not followed, communication may not be possible.