- The HTTP client and HTTP server exchange information about resources identified by URLs.
- HTTP headers allow the client and the server to pass additional information with the request or the response.
- ex)
GET /tutorials/other/top-20-mysql-best-practices/ HTTP/1.1
- method, path, protocol
- ex)
HTTP/1.x 200 OK
- A sequence of network request-response transactions.
- HTTP client initiates a request -> establishes a TCP connection to a particular port on a host -> wait for a client's request message -> the server receives the request and sends back a status line
- HTTP -> TCP -> server -> status
- similar to GET but w/o the response body.
- requests a representation of the specified resource.
- submits data to be processed to the identified resource.
- apply partial modification.
- deletes the specified resource.
- uploads a representation of the specified resource.
- echoes back the received request.
- returns the HTTP methods that the server supports for specified URL.
- converts the request connection to a transparent TCP/IP tunnel.
- methods that are intended only for information retrieval without changing the state of the server.
- In HTTP/1.1, a keep-alive-mechanism was introduced, where a connection could be reused for more than one request/response pair.
- a stateless protocol that does not require the server to retain information or status about each user for the duration of multiple requests. Often solved using HTTP cookies.