3 ms·
Do any browsers API's support quic ?
by neatze 4y ago
Do any browsers API's support quic ?
- bejelentkezni 4y agohttps://caniuse.com/http3 https://caniuse.com/http3
- ignoramous 4y agoLatest Chrome and Firefox both do. Make sure the server sends h3 with the alt-svc (http) header and adds h3 to the (tls v1.3) alpn. The browser may connect to h1 or h2 endpoints at first, then upgrading it to h3 for subsequent connections where supported (provided, the firewall isn't blocking QUIC). https://tools.ietf.org/id/draft-ietf-quic-http-23.html#rfc.section.3 https://tools.ietf.org/id/draft-ietf-quic-http-23.html#rfc.s...
- tialaramex 4y agoAlthough the newer HTTP protocols have ALPN names like h2 and h3, the older ones are named http/0.9, http/1.0 and http/1.1
- neatze 4y agoI mean if I can access it from javascript, like webrtc.
- aseipp 4y agoChrome actually has deployed a version of WebTransport, which is basically a way of using QUIC directly from the browser for datagram/stream connections (e.g. to implement game networking, in browser.) But it's relatively new, and you need to modify the QUIC stack in order to accept and handle WebTransport connections; so it doesn't "just work" out of the box with any popular QUIC libraries I know of. It's unclear where this will all end up right now; you'll probably have to wait a bit for it to be production ready. But there's clearly broad interest in the topic, though.
- Matthias247 4y agoIf you do a HTTP request in Javascript using any of the available APIs (fetch, XHR), it would automatically use HTTP/3 for those requests if the peer is known to understand HTTP/3. No special APIs are needed unless the protocol you care about is on top of QUIC but not actually using HTTP/3. As the sibling comment mentions, WebTransport might help with non-HTTP use-cases.