Muutke küpsiste eelistusi

Learning HTTP/2 [Pehme köide]

  • Formaat: Paperback / softback, 156 pages, kõrgus x laius x paksus: 232x179x9 mm, kaal: 270 g
  • Ilmumisaeg: 27-Jun-2017
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1491962445
  • ISBN-13: 9781491962442
  • Pehme köide
  • Hind: 39,09 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 45,99 €
  • Säästad 15%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Formaat: Paperback / softback, 156 pages, kõrgus x laius x paksus: 232x179x9 mm, kaal: 270 g
  • Ilmumisaeg: 27-Jun-2017
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1491962445
  • ISBN-13: 9781491962442
Demonstrates how the latest version of the Hypertext Transfer Protocol can dramatically improve website and application performance, in a book that explores performance challenges that led to the HTTP upgrade; HTTP/2 in a nutshell, including benefits and transition methods; how Google’s SPDY networking protocol paved the way for HTTP/2; and much more. Original.

What can your organization gain by adopting HTTP/2? How about faster, simpler, and more robust websites and applications? This practical guide demonstrates how the latest version of the Hypertext Transfer Protocol can dramatically improve website and application performance. You’ll take a deep dive into HTTP/2 details, and learn how this updated protocol is changing the web landscape.

HTTP/1.1 has been the primary means of communicating data across the Web for the past 20 years, but the level of interaction today has gone well beyond what people envisioned in 1997. With this book, authors Stephen Ludin and Javier Garza show you how HTTP/2 will help speed the execution of modern sites and applications.

With this book, you’ll explore:

  • Performance challenges that led to the HTTP upgrade
  • HTTP/2 in a nutshell, including benefits and transition methods
  • How Google’s SPDY networking protocol paved the way for HTTP/2
  • Existing best practices and hacks to improve web performance
  • HTTP/2 support for browsers, servers, proxies, and content delivery networks
  • How the performance of sites using HTTP/2 compares to their HTTP/1.1 experience—including the good, bad, and the ugly
  • HTTP/2’s effect on specific issues such as latency, packet loss, and Time to First Byte (TTFB)
Preface vii
Foreword xiii
1 The Evolution of HTTP
1(6)
HTTP/0.9 and 1.0
2(1)
HTTP/1.1
3(1)
Beyond 1.1
4(1)
SPDY
4(1)
HTTP/2
4(3)
2 HTTP/2 Quick Start
7(4)
Up and Running
7(1)
Get a Certificate
8(1)
Use an Online Generator
8(1)
Self Signed
8(1)
Let's Encrypt
8(1)
Get and Run Your First HTTP/2 Server
9(1)
Pick a Browser
10(1)
3 How and Why We Hack the Web
11(22)
Performance Challenges Today
11(10)
The Anatomy of a Web Page Request
11(3)
Critical Performance
14(2)
The Problems with HTTP/1
16(5)
Web Performance Techniques
21(12)
Best Practices for Web Performance
22(8)
Anti-Patterns
30(1)
Summary
31(2)
4 Transition to HTTP/2
33(8)
Browser Support
33(1)
Moving to TLS
34(2)
Undoing HTTP 1.1 "Optimizations"
36(2)
Third Parties
38(1)
Supporting Older Clients
38(1)
Summary
39(2)
5 The HTTP/2 Protocol
41(12)
Layers of HTTP/2
41(1)
The Connection
42(2)
Frames
44(3)
Streams
47(6)
Messages
48(3)
Flow Control
51(1)
Priority
52(1)
Server Push
53(12)
Pushing an Object
53(2)
Choosing What to Push
55(1)
Header Compression (HPACK)
56(2)
On the Wire
58(5)
A Simple GET
58(5)
Summary
63(2)
6 HTTP/2 Performance
65(26)
Client Implementations
65(2)
Latency
67(3)
Packet Loss
70(2)
Server Push
72(2)
Time to First Byte (TTFB)
74(2)
Third Parties
76(5)
HTTP/2 Anti-Patterns
81(2)
Domain Sharding
81(1)
Inlining
82(1)
Concatenating
82(1)
Cookie-less Domains
82(1)
Spriting
82(1)
Prefetch
83(1)
Real-World Performance
83(6)
Performance Measurement Methodology
84(1)
Study 1 www.facebook.com
84(2)
Study 2 www.yahoo.com
86(3)
Summary
89(2)
7 HTTP/2 Implementations
91(6)
Desktop Web Browsers
91(2)
TLS Only
91(1)
Disabling HTTP/2
92(1)
Support for HTTP/2 Server Push
92(1)
Connection Coalescing
92(1)
HTTP/2 Debugging Tools
92(1)
Beta Channel
93(1)
Mobile
93(1)
Mobile App Support
93(1)
Servers, Proxies, and Caches
94(1)
Content Delivery Networks (CDNs)
95(1)
Summary
95(2)
8 Debugging h2
97(20)
Web Browser Developer Tools
97(12)
Chrome Developer Tools
97(7)
Firefox Developer Tools
104(2)
Debugging h2 on iOS Using Charles Proxy
106(2)
Debugging h2 on Android
108(1)
WebPagetest
109(1)
OpenSSL
109(1)
OpenSSL Commands
110(1)
nghttp2
110(2)
Using nghttp
110(2)
curl
112(2)
Using curl
112(2)
h2i
114(1)
Wireshark
115(1)
Summary
116(1)
9 What Is Next?
117(4)
TCP or UDP?
117(1)
QUIC
118(1)
TLS 1.3
119(1)
HTTP/3?
120(1)
Summary
120(1)
A HTTP/2 Frames 121(10)
B Tools Reference 131(2)
Index 133
Stephen Ludin is a Chief Architect for Akamai's Site Acceleration and Security group. He joined Akamai in 2002 and works out of Akamai's west-coast headquarter in San Mateo, California. His primary focus has been on projects related to the core proxy technology that is responsible for routing, accelerating, and securing Akamai's traffic. Most recently, as a technology leader in the Web Acceleration team, he has been leading the efforts behind Akamai's next generation acceleration platform and its security and fraud prevention technology stack. Ludin received his degree from the University of California at San Diego in Computer Music where his coding abilities were used in writing C programs to create experimental music. We are all grateful for his decision to use his technical and management skill in a more aesthetically pleasing realm of making the web a faster and safer realm for commerce and communications.Javier Garza is a multi-lingual technology evangelist who loves taking things apart, understanding how they work, and finding the best/most practical way of improving them. He started hacking basic-based computer games at the age of 9, and has been working with computers for the past 25 years in Spain, Germany, and the US (half that time at Akamai helping the largest Websites on the Internet run faster and more secure).