Thruster is now open source
We’ve just released Thruster as open source! Thruster is a minimal HTTP/2 proxy server that we wrote to make it easier to serve a Rails application with great performance and security. It runs alongside your existing Puma process, and adds: HTTP/2 support SSL (via Let’s Encrypt, for automatic certificate management) HTTP caching, for public assets Efficient static file serving via X-Sendfile and c
HTTP/2 Rapid Reset: deconstructing the record-breaking attack
Starting on Aug 25, 2023, we started to notice some unusually big HTTP attacks hitting many of our customers. These attacks were detected and mitigated by our automated DDoS system. It was not long however, before they started to reach record breaking sizes — and eventually peaked just above 201 million requests per second. This was nearly 3x bigger than our previous biggest attack on record. Conc
HTTP/3 Prioritization Demystified
Robin Marx is a Web Performance Architect at Akamai Technologies. His main expertise is in network protocol performance, including HTTP/3 and QUIC, which was the topic of his PhD research. In a previous life he was a multiplayer game programmer and co-founder of LuGus Studios. YouTube videos of Robin are either humoristic technical talks or him hitting other people with longswords. If you deal wit
CEDEC2021 ダウンãƒãƒ¼ãƒˆã‚™æ™‚間を大幅減ï¼ï½žå¤§é‡ã®ã‚¢ã‚»ãƒƒãƒˆã‚’ã•ã¯ã‚™ã高速ãªå®Ÿè£…ã¨é‹ç”¨äº‹ä¾‹ã®å…±æœ‰ï½ž
2. © SEGA ゲームコンテンツ＆サービス事æ¥æœ¬éƒ¨ 技術本部 開発技術部 竹原 涼 自己紹介 ã€ç™»å£‡æ´ã€‘ CEDEC 2020 「技術åŒäººä½œå®¶ã«ãªã‚ㆠ～åƒã方改é©æ™‚代ã«ãŠã‘るエン ジニアã®ãƒ¬ãƒ™ãƒ«ã‚¢ãƒƒãƒ—ã®ä¸€ä¾‹ï½žã€ Unite Tokyo 2019 「大é‡ã®ã‚¢ã‚»ãƒƒãƒˆã‚‚怖ããªã„ï¼ï½žHTTP/2ã«ã‚ˆã‚‹é«˜ 速ãªé€šä¿¡ã®å®Ÿè£…例～〠CEDEC 2018ã€CEDEC 2016ã€CEDEC 2015 プãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³é–¢é€£ã®ãƒ© ウンドテーブル GDC2016 å ±å‘Šä¼š 「GDC16ã«ã¿ã‚‹è‡ªå‹•åŒ–技術ã¨ãƒ†ã‚¹ãƒˆã®ãƒˆãƒ¬ãƒ³ãƒ‰ã€ ç¥ãƒ»HTTP/3 RFC発行(é–“è¿‘)ï¼
Head-of-Line Blocking in QUIC and HTTP/3: The Details
Robin Marx is a Web Performance and network protocol researcher at Hasselt University, Belgium. He is mainly looking into HTTP/3 and QUIC performance, and develops the qlog and qvis tools to make this easier. In a previous life he was a multiplayer game programmer and co-founder of LuGus Studios. YouTube videos of Robin are either humoristic technical talks or him hitting other people with longswo
Chromeã®HTTP/2サーãƒãƒ—ッシュサãƒãƒ¼ãƒˆå»ƒæ¢æ¤œè¨Žã¨ã€103 Early Hintsã«ã¤ã„㦠- ASnoKaze blog
ChromeãŒHTTP/2サーãƒãƒ—ッシュã®å»ƒæ¢ã‚’検討ã—始ã‚ã¦ã„る。ã¾ãŸPreload + 103 Early Hintsã®æœ‰åŠ¹æ€§ã«ã¤ã„ã¦å®Ÿé¨“ã—ã¦ã„ã模様 背景 HTTP/2(RFC 7540) ã«ã¯ã‚µãƒ¼ãƒãƒ—ッシュã¨ã„ã†æ©Ÿèƒ½ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‹ã‚‰ã®HTTPリクエストをã¾ãŸãšã«ã‚µãƒ¼ãƒãŒHTTPレスãƒãƒ³ã‚¹ã‚’先行ã—ã¦é€ã‚‹ã“ã¨ãŒå‡ºæ¥ã‚‹æ©Ÿèƒ½ã§ã™ã€‚ ãŸã¨ãˆã°ã€index.htmlã«ç”»åƒ1,2,3ãŒå«ã¾ã‚Œã¦ã„るよã†ãªãƒšãƒ¼ã‚¸ãŒã‚ã‚‹ã¨ã—ã¾ã™ã€‚ã“ã®index.htmlã¸ã®ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’å—ã‘付ã‘ãŸã‚µãƒ¼ãƒã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãŒç”»åƒ1,2,3ãŒã‚’è¦æ±‚ã—ã¦ãã‚‹ã“ã¨ã‚’予測ã—サーãƒãƒ—ッシュã§ã“れらã®ãƒªã‚½ãƒ¼ã‚¹ã‚’é€ã‚Šã¤ã‘ã‚‹ã“ã¨ãŒæ¥ã§ã¾ã™ã€‚（クライアントå´ã‹ã‚‰ã€ãã®ãƒªã‚½ãƒ¼ã‚¹ãŒä¸è¦ã§ã‚ã‚Œã°ã‚µãƒ¼ãƒãƒ—ッシュをã‚ャンセルã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ï¼‰ ãã†ã™ã‚‹ã“ã¨ã§ã€ãƒšãƒ¼ã‚¸ã®è¡¨ç¤ºã‚’効率化出æ¥ã‚‹ã¨è€ƒãˆã‚‰ã‚Œã¦ã„ã¾ã—ãŸã€‚ ã—ã‹ã—ã€æ§˜ã€…ãªè°è«–ã®ä¸
Google Chrome does not do multiplexing with http2
I am building a webapp and serving it over http2. However when I analyze network in Google Chrome (Version 59.0.3071.115 (Official Build) (64-bit))'s developers tools, it is clear that multiplexing does not work as there are only 6 active connections (like with http1.1) and the rest of connections are queued. Why is this? Or are my expectations not correct? The screenshot (you can see that protoco
詳解HTTP/2 | 翔泳社
より高速ã§ã‚»ã‚ュアãªWebサイトã¯HTTP/2ã§å®Ÿç¾ã™ã‚‹ ã€æœ¬æ›¸ã®å†…容】 本書㯠Barry Pollard, "HTTP/2 in Action", Manning Publications 2019 ã®é‚¦è¨³ç‰ˆã§ã™ã€‚ ブラウザã¨Webサイトを繋ã標準的ãªãƒ—ãƒãƒˆã‚³ãƒ«ã¨ã—ã¦ã€ HTTPã¯æƒ³å®šã‚’é¥ã‹ã«è¶…ãˆã‚‹é•·ãã«æ¸¡ã£ã¦æ´»ç”¨ã•ã‚Œã¦ãã¾ã—ãŸã€‚ プãƒãƒˆã‚³ãƒ«ã«é™ã‚‰ãšã€ãŸã„ã¦ã„ã®æŠ€è¡“ã¯20年も経ã¦ã°ã€ ãªã«ã‹ã—らã®ä¸æº€ã‚„改善点ãŒè¦‹ãˆã¦ãã‚‹ã‚‚ã®ã§ã™ã€‚ 本書ã®ãƒ¡ã‚¤ãƒ³ãƒ†ãƒ¼ãƒžã§ã‚ã‚‹HTTP/2ã¯ç¾è¡Œã®HTTPã¨æ¯”ã¹ã¦ã€ ストリームやサーãƒãƒ¼ãƒ—ッシュã€ãƒ˜ãƒƒãƒ€ãƒ¼åœ§ç¸®ã‚„å„ªå…ˆé †ä½ä»˜ã‘をサãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ã§ã€ 速度ã€ã‚»ã‚ュリティã€åŠ¹çŽ‡æ€§ã‚’大幅ã«å‘上ã•ã›ã¾ã™ã€‚ 本書ã§ã¯HTTP/2ã®æ©æµã‚’最大é™ã«å—ã‘られるよã†ã€ 知ã£ã¦ãŠãã¹ãã“ã¨ã‚’詳細ã«é–‹ç¤ºã—ã¦ãã‚Œã¾ã™ã€‚ ãã‚Œã¯ãŸã¨ãˆã°ã€ãƒ•ãƒ¬ãƒ¼ãƒ ã®ã‚ˆã†ãªæ–°æ©Ÿèƒ½ã‚’使ã£ãŸ パフォーマンスã®æœ€
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
JVNVU#98433488: HTTP/2 ã®å®Ÿè£…ã«å¯¾ã™ã‚‹ã‚µãƒ¼ãƒ“スé‹ç”¨å¦¨å®³ (DoS) 攻撃手法
HTTP/2 通信ã®å‡¦ç†ã¯ã€HTTP/1.1 通信ã®å‡¦ç†ã¨æ¯”較ã—ã¦å¤šãã®ãƒªã‚½ãƒ¼ã‚¹ãŒå¿…è¦ã§ã‚ã‚Šã€RFC7540 ã® Security Considerations セクションã«ãŠã„ã¦ã‚‚ã€ã‚µãƒ¼ãƒ“スé‹ç”¨å¦¨å®³ (DoS) 状態ã«é–¢ã™ã‚‹æ¤œè¨ŽãŒè¡Œã‚ã‚Œã¦ã„ã¾ã™(10.5. Denial-of-Service Considerations)。ã—ã‹ã—ã€ã©ã®ã‚ˆã†ã«å¯¾ç–ã™ã¹ãã‹ã¯å®Ÿè£…者ã«ã¾ã‹ã•ã‚Œã¦ãŠã‚Šã€ã“ã‚ŒãŒä»¥ä¸‹ã®å•é¡Œã«ã¤ãªãŒã£ã¦ã„ã¾ã™ã€‚ Data Dribble - CVE-2019-9511 攻撃者ã¯è¤‡æ•°ã®ã‚¹ãƒˆãƒªãƒ¼ãƒ を通ã˜ã¦å¤§ããªã‚µã‚¤ã‚ºã®ãƒ‡ãƒ¼ã‚¿ã‚’リクエストã—ã€ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ã‚µã‚¤ã‚ºã‚„ストリームã®å„ªå…ˆé †ä½ã‚’æ“作ã—ã¦ã€ãƒ‡ãƒ¼ã‚¿ãŒ 1 ãƒã‚¤ãƒˆå˜ä½ã§å‡¦ç†ã•ã‚Œã‚‹ã‚ˆã†ã«ä»•å‘ã‘ã¾ã™ã€‚ã“れらã®ãƒ‡ãƒ¼ã‚¿ã‚’効率的ã«å‡¦ç†ã§ããªã‘ã‚Œã°ã€CPU, メモリã€ã‚‚ã—ãã¯ãã®ä¸¡æ–¹ãŒå¤§é‡ã«æ¶ˆè²»ã•ã‚Œã€ã‚µãƒ¼ãƒ“スé‹ç”¨å¦¨å®³ (DoS) 状態ãŒå¼•ãèµ·ã“ã•ã‚Œã‚‹å¯èƒ½
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
Cache Digest 㨠HTTP2 Server Push ã®ç¾çŠ¶ | blog.jxck.io
Intro httpbis ã®ãƒã‚§ã‚¢ã§ã‚ã‚‹ mnot ã‹ã‚‰ã€ Cache Digest ã«ã¤ã„ã¦ã®ç¾çŠ¶ç¢ºèªãŒ ML ã«æŠ•ç¨¿ã•ã‚ŒãŸã€‚ ã‚‚ã—ã“ã®ã¾ã¾åå¿œãŒãªã‘ã‚Œã°ã€ Cache Digest ã¯çµ‚ã‚ã‚Šã€å¯¾ãƒ–ラウザã‚ャッシュ㮠Server Push ã¯ç¾å®Ÿçš„ã§ã¯ãªããªã‚‹ã€‚ Update mozilla standard position ã« RFP を上ã’ãŸã¨ã“ã‚「実装ã¯ã—ãªã„ãŒä»•æ§˜ã«ã¤ã„ã¦ã¯ non-harmfulã€ã¨ãªã‚Šãã†ã 。 PFP: Cache Digest Issue #131 mozilla/standards-positions HTTP2 Push HTTP2 ã®ä»•æ§˜ç–定時ã«ç››ã‚Šè¾¼ã¾ã‚ŒãŸæ–°æ©Ÿèƒ½ã¨ã—ã¦ã€ Server Push ãŒã‚ã£ãŸã€‚ ã“ã‚Œã¯ã€ä¾‹ãˆã° RPC çš„ãªç”¨é€”ã§åŒæ–¹å‘性ã®ã‚る通信をå¯èƒ½ã«ã—ãŸã€‚ Web ã«ãŠã„ã¦ã¯ã€ãƒªã‚¯ã‚¨ã‚¹ãƒˆãŒæ¥ã‚‹å‰ã«ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã‚’è¿”ã—ã‚ャッシュã«å…¥ã‚Œ
日本語 - http2 explained
ã“ã®æ–‡æ›¸ã¯HTTP/2（RFC 7540）ã€ãã®èƒŒæ™¯ã€ã‚³ãƒ³ã‚»ãƒ—トã€ãƒ—ãƒãƒˆã‚³ãƒ«ã€æ—¢å˜ã®å®Ÿè£…ãŠã‚ˆã³æœªæ¥ãŒã©ã†ãªã‚‹ã‹ã‚’記述ã—ãŸã‚‚ã®ã§ã™ã€‚ ã“ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ã‚µã‚¤ãƒˆã¯ https://daniel.haxx.se/http2/ を見ã¦ãã ã•ã„。 文書ã®å…¨ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã¯ https://github.com/bagder/http2-explained を見ã¦ãã ã•ã„。
ã¯ã˜ã‚ã¦ã®HTTP/2 - 8pockets - BOOTH
技術書典5ã§ã®æ–°ä½œã®ã€Œã¯ã˜ã‚ã¦ã®HTTP/2ã€ã®PDF版ã§ã™ã€‚（サークルå「サティファクï¼ã€ï¼‰ å½“æ—¥ä¼šå ´ã«è¡Œã‘ãªã„ã®ã§ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰è²©å£²ã—ã¦ã»ã—ã„ã€ã¨ã®å£°ãŒã‚ã£ãŸã®ã§ã“ã¡ã‚‰ã§ã‚‚販売ã„ãŸã—ã¾ã™ã€‚ 本書㯠・HTTP/2ã®åå‰ã¯èžã„ãŸã“ã¨ã¯ã‚ã‚‹ã‘ã©ã¾ã 良ã知らãªã„ ・HTTPを普段使ã†ã‘ã©ã€æ–°ã—ã„技術をã¾ã ã‚ャッãƒã‚¢ãƒƒãƒ—ã§ãã¦ã„ãªã„ ã®ã‚ˆã†ãªæ–¹ã‚’ターゲットã¨ã—ã¦ã„ã¾ã™ã€‚ 標準化ãŒè¡Œã‚ã‚Œã¦å¤§ãã広ã¾ã‚Šã¤ã¤ã‚ã‚‹HTTP/2ã‚’æ—©ã‚ã«å¦ã‚“ã§ãŠãã“ã¨ã§ã€çš„確ãªæŠ€è¡“力を身ã«ã¤ã‘られるã¨åŸ·ç†ã—ãªãŒã‚‰æ„Ÿã˜ã¾ã—ãŸã€‚ 技術書典5ã§ã¯1時間ã»ã©ã§å®Œå£²ã—ã¦ã—ã¾ã£ãŸãŸã‚〠次回ã®æŠ€è¡“書典ã§ã®å†Šå版ã¯ã‚ˆã‚Šå¤šãã®å†Šæ•°ã‚’ã”用æ„ã—ã¾ã™...ï¼ =================== NHKã®æŠ€è¡“書典ã®æ”¾é€ã§ã€Œã¯ã˜ã‚ã¦ã®HTTP/2ã€ã®æ›¸ç±ãŒå°‘ã—ç™»å ´ã—ã¾ã—ãŸï¼ ãƒãƒƒãƒˆã®è¨˜äº‹ã§ã‚‚HTTPã«ã¤ã„ã¦å°‘ã—ã ã‘触れã¦é ‚ãã¾ã—ãŸã€‚ https
Optimizing HTTP/2 prioritization with BBR and tcp_notsent_lowat
Optimizing HTTP/2 prioritization with BBR and tcp_notsent_lowat2018-10-12 Getting the best end-user performance from HTTP/2 requires good support for resource prioritization. While most web servers support HTTP/2 prioritization, getting it to work well all the way to the browser requires a fair bit of coordination across the networking stack. This article will expose some of the interactions betwe
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Node 18.13 HTTP/2 live lock · Issue #46234 · nodejs/node
GitHub - bcoe/http2spy: test helpers for working with Node.js' http2 module
GitHub - andydavies/http2-prioritization-issues: Tracks issues / notes for HTTP/2 prioritization across browsers, CDNs and servers
よãã‚ã‹ã‚‹HTTP/2ã®æ•™ç§‘書 | 後藤 ゆã |本 | 通販 | Amazon
1434137 - Implement websockets over http/2
{{#tags}}- {{label}}
{{/tags}}