HTTP/2: Faster and better than HTTP 1.1, but is it more secure? | ImpervaImperva named a security leader in the SecureIQlab CyberRisk ReportGet featured report
Real–world HTTP/2: 400gb of images per day - 99designs
The now–finalized HTTP/2 specification has rightfully garnered a lot of interest from the web performance community. The new protocol is aimed at addressing common network performance issues with the aging HTTP/1.x protocol, whilst preserving the existing semantics. We began a small-scale rollout for static assets earlier this year. After building confidence in our new infrastructure, we began tra
Developing the fastest HTTP/2 server
This presentation will demonstrate that permanent backdooring of hardware is practical. We have built a generic proof of concept malware for the intel architecture, Rakshasa, capable of infecting more than a hundred of different motherboards. The first net effect of Rakshasa is to disable NX permanently and remove SMM related fixes from the BIOS, resulting in permanent lowering of the security of
Open sourcing our NGINX HTTP/2 + SPDY code
In December, we released HTTP/2 support for all customers and on April 28 we released HTTP/2 Server Push support as well. The release of HTTP/2 by CloudFlare had a huge impact on the number of sites supporting and using the protocol. Today, 50% of sites that use HTTP/2 are served via CloudFlare. CC BY 2.0 image by JD Hancock When we released HTTP/2 support we decided not to deprecate SPDY immediat
Announcing Support for HTTP/2 Server Push
Last November, we rolled out HTTP/2 support for all our customers. At the time, HTTP/2 was not in wide use, but more than 88k of the Alexa 2 million websites are now HTTP/2-enabled. Today, more than 70% of sites that use HTTP/2 are served via CloudFlare. CC BY 2.0 image by Roger Price HTTP/2’s main benefit is multiplexing, which allows multiple HTTP requests to share a single TCP connection. This
Http2 on go1.6rc2
This document discusses HTTP/2 support in Go 1.6. It notes that the net/http package now supports HTTP/2 out of the box. It provides code samples showing how a server can be configured with and without HTTP/2 support. It also describes how HTTP/2 functionality like HPACK header compression, server push, flow control, and priority are implemented in Go net/http. Finally, it summarizes the current l
HTTP2 ã‚’å‰æã¨ã—㟠HTML+CSS コンãƒãƒ¼ãƒãƒ³ãƒˆã®ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ãƒ‘ス最é©åŒ–ã«ã¤ã„㦠| blog.jxck.io
Intro Chrome ãŒäºˆå®šã—ã¦ã„ã‚‹ <link rel=stylesheet> ã®æŒ™å‹•ã®å¤‰æ›´ã«ã¤ã„ã¦ã€ Google Chrome ãƒãƒ¼ãƒ ã® Jake ãŒã€èˆˆå‘³æ·±ã„ブãƒã‚°ã‚’上ã’ã¦ã„る。 The future of loading CSS ã“ã®å†…容ã¯ã€å˜ã« Chrome ã«å¯¾ã™ã‚‹å¤‰æ›´ã ã‘ã§ã¯ãªã〠HTTP2 ã«ã‚ˆã£ã¦å¤‰åŒ–ã™ã‚‹æœ€é©åŒ–手法ã¨ã€ãれを最も活ã‹ã™ãŸã‚ã® HTML, CSS ã®æ§‹æˆã«ã¤ã„ã¦ã®ãƒ’ントãŒã‚る。 今回ã¯ã€ã“ã®å†…容をæ„訳+補足解説ã—ã€æœ¬ã‚µã‚¤ãƒˆã«é©ç”¨ã—ã¦ã„ã。 HTTP/1.1 時代㮠CSS HTML 自体ãŒã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆã‚’æ„è˜ã—ãŸä½œã‚Šã«ãªã£ã¦ã„ã‚‹å ´åˆã¯ã€è‡ªç„¶ã¨ CSS ã‚‚ class ãªã©ã‚’使ã„コンãƒãƒ¼ãƒãƒ³ãƒˆå˜ä½ã«ä½œã‚‹ã“ã¨ãŒã§ãã‚‹ã ã‚ã†ã€‚ ã—ã‹ã—〠HTTP/1.1 ã§ã¯ã€ãƒªã‚¯ã‚¨ã‚¹ãƒˆã®æ•°ã‚’減らã™ãŸã‚ã«å…¨ã¦ã® CSS ã‚’ 1 ã¤(ã‚‚ã—ãã¯å°‘数個)ã«çµåˆã™ã‚‹æœ€é©åŒ–ãŒä¸»æµã
Cache Digests for HTTP/2 - draft-kazuho-h2-cache-digest-00
Abstract This specification defines a HTTP/2 frame type to allow clients to inform the server of their cache's contents. Servers can then use this to inform their choices of what to push to clients. Note to Readers The issues list for this draft can be found at https://github.com/mnot/I-D/labels/h2-cache-digest . The most recent (often, unpublished) draft is at https://mnot.github.io/I-D/h2-cache-
Third party content in an HTTP/2 and ad blockers world
Yoav Weiss (@yoavweiss) does not get discouraged easily and is not afraid of code. He is a Web performance and browser internals specialist, especially interested in the intersection between Responsive Web Design and Web performance. He has implemented the various responsive images features in Blink and WebKit as part of the Responsive Images Community Group, and is currently working at Akamai, fo
HTTP/2 ã‹ã‚‰ QUIC ã¸ç¶šã Web プãƒãƒˆã‚³ãƒ«ã®é€²åŒ– - 151111_4.pdf
HTTP/2ã‹ã‚‰QUICã¸ç¶šã Webプãƒãƒˆã‚³ãƒ«ã®é€²åŒ– 大津 ç¹æ¨¹ IIJ Technical WEEK 2015 2015å¹´11月11æ—¥ 自己紹介 • 大津 ç¹æ¨¹ • æ ªå¼ä¼šç¤¾ インターãƒãƒƒãƒˆã‚¤ãƒ‹ã‚·ã‚¢ãƒ†ã‚£ãƒ– • プãƒãƒ€ã‚¯ãƒˆæœ¬éƒ¨ アプリケーション開発部サービス開発2課 • NodeJS Technical Steering Committee メンãƒãƒ¼ • (主ã«TLS/CRYPTO/OpenSSLãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°ã‚’担当） • IETF httpbis WG 㧠HTTP/2相互接続試験ç‰ä»•æ§˜ç–定ã«å‚画。 内容 Webプãƒãƒˆã‚³ãƒ«ã®é€²åŒ–ã¨ã“ã‚Œã‹ã‚‰ã«ã¤ã„ã¦æ¬¡ã®ãƒ•ã‚§ãƒ¼ã‚ºæ¯Žã«ã㮠概è¦ã¨è¦‹é€šã—を解説ã—ã¾ã™ã€‚ 1. HTTP/1.1 ã‹ã‚‰HTTP/2㸠2. HTTP/2 ã‹ã‚‰QUIC 㸠3. QUIC ã‹ã‚‰TLS1.3(*) 㸠(*注æ„) 内容ã¯2015å¹´11月2日時点ã§ã® TLS1.3 dra
HTTP/2 is here! Goodbye SPDY? Not quite yet
HTTP/2 is here! Goodbye SPDY? Not quite yet2015-12-03 Why choose, if you can have both? Today CloudFlare is introducing HTTP/2 support for all customers using SSL/TLS connections, while still supporting SPDY. There is no need to make a decision between SPDY or HTTP/2. Both are automatically there for you and your customers. If you are a customer on the Free or Pro plan, there is no need to do anyt
Integralist
HTTP/2TOC Introduction This is a super quick post for demonstrating how to utilise the new HTTP/2 protocol. If you’re unfamiliar with it, then let me spend a brief few moments discussing some of the highlights. Persistent Connections When using HTTP/1.x each resource your web page specified would need its own connection. If you had three images on a page then that would be three separate connectio
Cache aware-server-push in H2O version 1.5
This document discusses cache-aware server push in H2O version 1.5. It describes calculating a fingerprint of cached assets using a Golomb compressed set to identify what assets need to be pushed from the server. It also discusses implementing this fingerprint using a cookie or service worker. The hybrid approach stores responses in the service worker cache and updates the cookie fingerprint. H2O
The Case for HTTP/2
HTTP/2 addresses limitations in HTTP/1.x by multiplexing requests over a single TCP connection, compressing headers, and allowing servers to push responses. It leads to more efficient use of network resources and faster page loads. While browser support is good, server implementations are still maturing and need to fully support HTTP/2 features like streams, dependencies, and server push to provid
å‰æ–¹ç§˜åŒ¿æ€§ (forward secrecy) ã‚’ã‚‚ã¤ã‚¦ã‚§ãƒ–サイトã®æ£ã—ã„è¨å®šæ–¹æ³•
å‰æ–¹ç§˜åŒ¿æ€§ï¼ˆforward secrecy）ã¨ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªæ€§è³ªã‚’指ã—ã¾ã™ã€‚ 公開éµæš—å·ã®ç§˜å¯†éµã®ã‚ˆã†ã«ã€æ¯”較的長期ã«æ¸¡ã£ã¦ä½¿ã‚れるéµãŒæ¼ãˆã„ã—ãŸã¨ãã§ã‚‚ã€ãã‚Œã¾ã§é€šä¿¡ã—ã¦ã„ãŸæš—å·æ–‡ãŒè§£èªã•ã‚Œãªã„ã¨ã„ã†æ€§è³ª éµãŒæ¼ã‚Œã‚‹ã“ã¨ã‚‚想定ã›ã‚ˆâ€•â€•ã‚¯ãƒ©ã‚¦ãƒ‰æ™‚代ã«ãŠã‘る「楕円曲線暗å·ã€ã®å¿…然性 - @IT éµãŒæ”»æ’ƒè€…ã‚„è«œå ±æ©Ÿé–¢ãªã©ç¬¬ä¸‰è€…ã®çŸ¥ã‚‹ã¨ã“ã‚ã¨ãªã£ãŸå ´åˆã§ã‚‚ã€ãã‚Œã¾ã§é€šä¿¡ã—ã¦ã„ãŸæš—å·æ–‡ãŒè§£èªã•ã‚Œãªã„よã†ã«ã—ãªã„ã¨ã„ã‘ãªã„ã€ã¨ã„ã†è€ƒãˆæ–¹ã¨ã¨ã‚‚ã«ã€æœ€è¿‘ HTTPS を利用ã™ã‚‹ã‚¦ã‚§ãƒ–サイトã«ãŠã„ã¦ã‚‚å°Žå…¥ãŒæ±‚ã‚られるよã†ã«ãªã£ã¦ããŸæ¦‚念ã§ã™ã€‚ å‰æ–¹ç§˜åŒ¿æ€§ã‚’満ãŸã™ã‚¦ã‚§ãƒ–サイトã®è¨å®šæ–¹æ³•ã«ã¤ã„ã¦ã¯ã€TLSã®æš—å·åŒ–æ–¹å¼ã‚’ECDH_RSAã‚ã‚‹ã„ã¯ECDHE_RSAã«è¨å®šã™ã‚Œã°è‰¯ã„ã€ã¨è¿°ã¹ã¦ã„る文献ãŒå¤šã„ã§ã™ã€‚ ã§ã™ãŒã€ã»ã¨ã‚“ã©ã®ã‚¦ã‚§ãƒ–サーãƒã«ãŠã„ã¦ã€ãã‚Œã¯èª¤ã‚Šã§ã™ã€‚ ãªãœã‹ã€‚ 通信を暗å·åŒ–ã™ã‚‹éµï¼ˆã‚»ãƒƒã‚·ãƒ§ãƒ³éµï¼‰
H2Oã®mrubyæ‹¡å¼µãŒå®Ÿç”¨çš„ã«ãªã£ã¦ããŸä»¶ - 人間ã¨ã‚¦ã‚§ãƒ–ã®æœªæ¥
H2Oã«mrubyæ‹¡å¼µã®æ案を行ã„mergeã•ã‚Œã¦ã‹ã‚‰å¹¾ã¤ã‹ã®PRを経ã¦ã€å°‘ã—ãšã¤å®Ÿç”¨çš„ã«ãªã£ã¦ãã¾ã—ãŸã€‚ github.com 今日ã¯ç°¡å˜ã«ãã®ä½¿ã„方を紹介ã—よã†ã¨æ€ã„ã¾ã™ã€‚ h2o_mrubyを有効化ã—ãŸh2oをビルド h2o_mrubyを有効化ã—ã¦ãƒ“ルドã™ã‚‹ã®ã¯ç°¡å˜ã§ã€OSã®ãƒ©ã‚¤ãƒ–ラリ環境（/usr/lib/以下ã¨ã‹ï¼‰ã«libmruby.aç‰ã®mrubyライブラリãŒã‚る状態ã§ã€ cmake -DWITH_MRUBY=ON . make h2o ã™ã‚‹ã ã‘ã§ã€h2o_mrubyãŒæœ‰åŠ¹åŒ–ã•ã‚ŒãŸh2oãƒã‚¤ãƒŠãƒªãŒã‚«ãƒ¬ãƒ³ãƒˆã«ãƒ“ルドã•ã‚Œã¾ã™ã€‚ç°¡å˜ã§ã™ã。 ã¾ãŸã“ã®è¨˜äº‹ã‚‚å‚考ã«ã™ã‚‹ã¨è‰¯ã„ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 qiita.com 使ãˆã‚‹ãƒ¡ã‚½ãƒƒãƒ‰ mod_mrubyã‚„ngx_mruby程メソッドã¯ã¾ã 充実ã—ã¦ã„ã¾ã›ã‚“ãŒã€å°‘ã—ãšã¤ä½¿ãˆã‚‹ã‚‚ã®ã‚’実装ã—ã¦ã„ã¾ã™ã€‚ã¾ãŸã€mod_mrubyã‚„ngx_mrubyã¨ã®äº’æ›
Peer-to-peer Extension to HTTP/2
Hypertext Transfer Protocol Working Group C. Benfield Internet-Draft July 20, 2015 Intended status: Standards Track Expires: January 21, 2016 Peer-to-peer Extension to HTTP/2 draft-benfield-http2-p2p-00 Abstract This document introduces a negotiated extension to HTTP/2 that turns a single HTTP/2 connection into a bi-directional communication channel. Status of This Memo This Internet-Draft is subm
ランã‚ング
障害
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
http2/quic meetup summary
HTTP2 時代㮠Web - web over http2
Compression Ratio
{{#tags}}- {{label}}
{{/tags}}