How Facebook is bringing QUIC to billions
We are replacing the de facto protocol the internet has used for decades with QUIC, the latest and most radical step we’ve taken to optimize our network protocols to create a better experience for people on our services. Today, more than 75 percent of our internet traffic uses QUIC and HTTP/3 (we refer to QUIC and HTTP/3 together as QUIC). QUIC has shown significant improvements in several metrics
The state of QUIC and HTTP/3 2020
Why FastlyProductsServicesSolutionsDevelopersPartnersResourcesPricing The state of QUIC and HTTP/3 2020QUIC — a latency-reducing, reliable, and secure transport protocol — and HTTP/3 — a mapping of HTTP semantics on top of QUIC — are co-evolving protocols that are being developed and deployed in tandem. This regularly updated blog post will elaborate on the current state of the protocols, their de
QUICã®å®Ÿè£…ã¯TCP並ã¿ã®åŠ¹çŽ‡ã‚’実ç¾ã§ãã‚‹ã‹ï¼Ÿ Fastly奥æ°ã‚‰ãŒãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ã‚’紹介
ç¾åœ¨æ¨™æº–化ãŒé€²ã‚られã¦ã„る次世代HTTPã®ã€ŒHTTP/3ã€ã¯ã€ãƒˆãƒ©ãƒ³ã‚¹ãƒãƒ¼ãƒˆãƒ—ãƒãƒˆã‚³ãƒ«ã¨ã—ã¦ã€ŒQUICã€ã¨å‘¼ã°ã‚Œã‚‹æ–°ã—ã„プãƒãƒˆã‚³ãƒ«ã‚’採用ã—ã¾ã™ã€‚ ç¾æ™‚点ã®HTTPã¯ãƒˆãƒ©ãƒ³ã‚¹ãƒãƒ¼ãƒˆãƒ—ãƒãƒˆã‚³ãƒ«ã¨ã—ã¦ã€ŒTCPã€ãŒæŽ¡ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚ãã®ä¸Šã§ã€å¯èƒ½ãªé™ã‚Šé«˜é€Ÿãªé€šä¿¡ãŒè¡Œãˆã‚‹ã‚ˆã†ã«ã•ã¾ã–ã¾ãªå·¥å¤«ã‚„最é©åŒ–ãŒé€²ã‚られã¦ãã¾ã—ãŸã€‚ãã—ã¦ã‚‚ã†ã“れ以上高速ã«ã—よã†ã¨ã™ã‚‹ã¨ã€TCPãã®ã‚‚ã®ã‚’改善ã—ã¦ã„ãã¹ãã ã‚ã†ã€ã¨ã„ã†ã¨ã“ã‚ã¾ã§ããŸã®ã§ã™ã€‚ ãã‚ŒãŒHTTP/3ã§ã€ŒQUICã€ãŒæŽ¡ç”¨ã•ã‚Œã‚‹å¤§ããªç†ç”±ã¨ã„ã‚ã‚Œã¦ã„ã¾ã™ã€‚ TCPã¯å†…部ã§è¼»è¼³åˆ¶å¾¡ã‚„å†é€ãªã©ã‚’自動的ã«è¡Œã†ã“ã¨ã§é€šä¿¡ãŒç¢ºå®Ÿã«è¡Œã‚れるã“ã¨ã‚’ä¿è¨¼ã—ã¦ãれる便利ãªãƒ—ãƒãƒˆã‚³ãƒ«ã§ã™ãŒã€ãれゆãˆã«ã€ç¢ºå®Ÿã«é€šä¿¡ãŒè¡Œã‚れるã¾ã§å¾…ã¤å¿…è¦ãŒã‚ã‚‹ãŸã‚ã«é€šä¿¡ç’°å¢ƒã«ã‚ˆã£ã¦ã¯é…ããªã‚ŠãŒã¡ã€ãªã©ã®å´é¢ãŒã‚ã‚Šã¾ã™ã€‚ ãã“ã§QUICã¯ã€TCPã®ã‚ˆã†ãªé€šä¿¡ã®ä¿è¨¼ãŒãªã„代ã‚ã‚Šã«ãƒªã‚¢ãƒ«ã‚¿ã‚¤ãƒ 性ã®é«˜ã„
Comparing HTTP/3 vs. HTTP/2 Performance
We announced support for HTTP/3, the successor to HTTP/2 during Cloudflare’s birthday week last year. Our goal is and has always been to help build a better Internet. Collaborating on standards is a big part of that, and we're very fortunate to do that here. Even though HTTP/3 is still in draft status, we've seen a lot of interest from our users. So far, over 113,000 zones have activated HTTP/3 an
nghttp3を使ã£ã¦curlã§HTTP/3通信ã™ã‚‹ - Qiita
CloudflareãŒä½œæˆã—ãŸrust製ã®QUICライブラリã€quicheを使ã£ãŸcurlã§ã®HTTP/3通信ã¯ä»¥å‰ã®è¨˜äº‹ã‚’使ã£ã¦å®Ÿç¾ã§ãã¾ã—ãŸãŒã€ngtcp2ã¨nghttp3を使ã£ãŸcurlã®ãƒ“ルドãŒä¸Šæ‰‹ãã„ã‹ãšã€æ”¾ç½®ã—ã¦ã¾ã—ãŸã€‚ 今日やã£ã¦ã¿ãŸã‚‰å‹•ãよã†ã«ãªã£ã¦ãŸã®ã§ã†ã‚Œã´ãƒ¼ã£ã¦æ„Ÿã˜ã§ã™ã€‚ ã“ã‚“ãªã‹ã‚“ã˜ã€‚ $ docker run --rm -it inductor/curl-quic-ngtcp2 # curl --http3 https://facebook.com/ curl --http3 https://www.facebook.com/ -v -s -o /dev/null * Trying 31.13.82.36:443... * Connect socket 3 over QUIC to 31.13.82.36:443 * QUIC handshake is compl
Better HTTP/2 Prioritization for a Faster Web
HTTP/2 promised a much faster web and Cloudflare rolled out HTTP/2 access for all our customers long, long ago. But one feature of HTTP/2, Prioritization, didn’t live up to the hype. Not because it was fundamentally broken but because of the way browsers implemented it. Today Cloudflare is pushing out a change to HTTP/2 Prioritization that gives our servers control of prioritization decisions that
Application Load Balancer can now Invoke Lambda Functions to Serve HTTP(S) Requests
Application Load Balancers now support invoking Lambda functions to serve HTTP(S) requests. This enables users to access serverless applications from any HTTP client, including web browsers. With the Application Load Balancers' support for content-based routing rules, you can also route requests to different Lambda functions based on the request content. Prior to this launch, you could only use EC
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
README | HTTP/3 explained
{{#tags}}- {{label}}
{{/tags}}