15 votes

HTTP/3

Posted by unknown user
Tags: http, tcp, udp, quic
https://daniel.haxx.se/blog/2018/11/11/http-3/

Link information

This data is scraped automatically and may be incorrect.

Title
daniel.haxx.se
Authors
Daniel Stenberg
Published
Nov 11 2018
Word count
287 words

5 comments

  1. [2]
    unknown user
    (edited )
    Link
    An interesting explanation of QUIC can be found over there. Another interesting article is “How unreliable is UDP?”.
    • Exemplary

    An interesting explanation of QUIC can be found over there.

    Another interesting article is “How unreliable is UDP?”.

    4 votes
  2. [3]
    teaearlgraycold
    Link
    I don't really know anything about QUIC or what's happening here. But does this mean that HTTP 3 will be encrypted only? Not having de-facto encryption was the biggest failing of HTTP 2.

    Originally, QUIC was started as an effort by Google and then more of a "HTTP/2-encrypted-over-UDP" protocol.

    I don't really know anything about QUIC or what's happening here. But does this mean that HTTP 3 will be encrypted only? Not having de-facto encryption was the biggest failing of HTTP 2.

    3 votes
    1. unknown user
      Link Parent
      IIRC, HTTP/2 is already TLS-only in browsers. At least I remember the Chrome people saying that they won't add unencrypted HTTP/2 to the browser. The Wiki confirms:

      IIRC, HTTP/2 is already TLS-only in browsers. At least I remember the Chrome people saying that they won't add unencrypted HTTP/2 to the browser. The Wiki confirms:

      Although the standard itself does not require usage of encryption, all major client implementations (Firefox, Chrome, Safari, Opera, IE, Edge) have stated that they will only support HTTP/2 over TLS, which makes encryption de facto mandatory.

      8 votes
    2. spit-evil-olive-tips
      Link Parent
      According to the spec, HTTP/2 doesn't require encryption. According to actual commonly-used implementations, HTTP/2 without TLS is not supported. Which overall seems like a pragmatic decision to...

      Not having de-facto encryption was the biggest failing of HTTP 2.

      According to the spec, HTTP/2 doesn't require encryption.

      According to actual commonly-used implementations, HTTP/2 without TLS is not supported.

      Which overall seems like a pragmatic decision to me...allow SSL/TLS to evolve at a different rate compared to HTTP itself.

      4 votes