HTTP/1.1
[RESTful](https://texonom.com/restful-cddc821aa86e42ccab831ecfc22c007d) [HTTPS](https://texonom.com/https-055d5ea9284841cb86885c0848ddeb4d) [HTTP Verb](https://texonom.com/http-verb-bf6fcc307e1a42868dac627435e81578) 


## The first standardized version of HTTP
published in early 1997, only a few months after HTTP/1.0
supports seven methods: OPTIONS, GET, HEAD, POST, PUT, DELETE, and TRACE
기본적으로 Connection당 하나의 요청을 처리 하도록 설계
동시전송이 불가능하고 요청과 응답이 순차적
1. DNS 조회. 호스트 이름에 대해서 DNS 조회 후 연결할 IP주소를 확보
2. TCP 연결을 위한 핸드쉐이크
3. TLS 연결을 위한 핸드쉐이크
4. HTTP 요청 전송
5. HTTP 응답 수신


## Historic Accidents
- RFC 5789 added PATCH in 2010
- RFC 7231 added CONNECT in 2014
- HTTPS emerged
- Roy Fielding led a group of experts that invented REST



- representation
- content negotiation
- variant
- cachable
- first-hand
- explicit expiration time
- heuristic expiration time
- age
- freshness lifetime
- fresh
- stale
- semantically transparent
- validator



### Enhancement
- Virtual hosting allows multiple domains to be served from a single IP address
- The persistent and pipelined connections allow a web browser to send multiple requests over a single persistent connection
- **The chunked encoding allows a response to be sent before its total length is known. This enables dynamically generated pages**






> [rfc2068](https://datatracker.ietf.org/doc/html/rfc2068)

> [QUIC과 HTTP/3 - 2. 기존의 성능 개선 기법 및 한계](https://www.saturnsoft.net/network/2019/03/26/quic-http3-2/)






Roy Fielding led a group of experts that invented REST