HTTP/3

1 min read

track http redirection

http://wubigo.com/post -> http://wubigo.com/post/ -> https://wubigo.com/post/

curl -IL http://wubigo.com/post

HTTP/1.1 301 Moved Permanently
Location: https://wubigo.com/post
Via: 1.1 varnish
X-Cache: HIT
X-Cache-Hits: 1

HTTP/1.1 200 OK
Content-Length: 0

HTTP/1.1 301 Moved Permanently
Strict-Transport-Security: max-age=31556952
Location: http://wubigo.com/post/
Access-Control-Allow-Origin: *
X-Cache: HIT
X-Cache-Hits: 1


HTTP/1.1 301 Moved Permanently
Location: https://wubigo.com/post/
X-Cache: HIT
X-Cache-Hits: 1

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: max-age=600
X-Cache: HIT
X-Cache-Hits: 1

main goal

  • HTTP/2’s multiplexed connections, allowing multiple streams of data to reach all the endpoints independently. In contrast, HTTP hosted on Transmission Control Protocol (TCP) can be blocked if any of the multiplexed data streams has an error.

  • reduced connection and transport latency, and bandwidth estimation in each direction to avoid congestion. It also moves control of the congestion avoidance algorithms into the application space at both endpoints, rather than the kernel space, which it is claimed will allow these algorithms to improve more rapidly. Additionally, the protocol can be extended with forward error correction (FEC) to further improve performance when errors are expected

[1]. revive Gopherspace

[2]. gopher client

HTTP WEB

Related