Enviar pesquisa
Carregar
Akamai Korea - Tech Day (2015/03/11) HTTP/2
•
72 gostaram
•
6,131 visualizações
SangJin Kang
Seguir
Akamai Korea - Tech Day (2015/03/11) HTTP/2
Leia menos
Leia mais
Internet
Denunciar
Compartilhar
Denunciar
Compartilhar
1 de 47
Baixar agora
Baixar para ler offline
Recomendados
Akamai 서비스 트러블 슈팅 및 테스트 방법과 도구
Akamai 서비스 트러블 슈팅 및 테스트 방법과 도구
SangJin Kang
Akamai Korea - Tech Day (2015/03/11) DNS
Akamai Korea - Tech Day (2015/03/11) DNS
SangJin Kang
Real world experiences with HTTP/2 (Michael Gooding, Javier Garza from Akamai)
Real world experiences with HTTP/2 (Michael Gooding, Javier Garza from Akamai)
💻 Javier Garza
Edge 2016 h2 in the real world
Edge 2016 h2 in the real world
akamaidevrel
Edge 2016 service workers and other front end techniques
Edge 2016 service workers and other front end techniques
akamaidevrel
Hans Nipshagen (Akamai) | TU - Hack & Attacks
Hans Nipshagen (Akamai) | TU - Hack & Attacks
Media Perspectives
Content Growth by Kams Yueng
Content Growth by Kams Yueng
MyNOG
EDNS0 Client-Subnet for DNS based CDNs by Matt Jansen
EDNS0 Client-Subnet for DNS based CDNs by Matt Jansen
MyNOG
Mais conteúdo relacionado
Mais procurados
Future of CDN - Next 10 Years - Ahmet Ozalp, Akamai Technologies - DigiWorld ...
Future of CDN - Next 10 Years - Ahmet Ozalp, Akamai Technologies - DigiWorld ...
IDATE DigiWorld
Edge 2016 keeping tls secure
Edge 2016 keeping tls secure
akamaidevrel
Open source Cloud Automation Platform
Open source Cloud Automation Platform
Kishore Neelamegam
Metrics, metrics everywhere (but where the heck do you start?)
Metrics, metrics everywhere (but where the heck do you start?)
Tammy Everts
Incapsula: How to Increase SaaS Websites’ Uptime and Accelerate Performance
Incapsula: How to Increase SaaS Websites’ Uptime and Accelerate Performance
Imperva Incapsula
Gwava gwava6
Gwava gwava6
GWAVA
A Modern Approach to Performance Monitoring
A Modern Approach to Performance Monitoring
Cliff Crocker
Configs, Configs, Everywhere! (Actually, Let's Simplify All Those Configs)
Configs, Configs, Everywhere! (Actually, Let's Simplify All Those Configs)
Akamai Developers & Admins
VMware 2V0-21.20 Practice Test
VMware 2V0-21.20 Practice Test
Armstrongsmith
Veeam Availability Suite version 10
Veeam Availability Suite version 10
Tanawit Chansuchai
Belgrade when its just too slow
Belgrade when its just too slow
Doug Sillars
Qa fest kiev_when its just too slow
Qa fest kiev_when its just too slow
Doug Sillars
Speed Up WordPress Websites - Part 1 - WordPress Cairo Meetup
Speed Up WordPress Websites - Part 1 - WordPress Cairo Meetup
Ahmed Mohammed Nagdy
Hacking Web Performance
Hacking Web Performance
Maximiliano Firtman
Cloud Security: Attacking The Metadata Service
Cloud Security: Attacking The Metadata Service
Puma Security, LLC
Metrics, Metrics Everywhere (but where the heck do you start?)
Metrics, Metrics Everywhere (but where the heck do you start?)
SOASTA
Cloud based Performance Testing
Cloud based Performance Testing
Impetus Technologies
IBC Content Everywhere Hub Presentation: HTML5 And Fastest Encoding
IBC Content Everywhere Hub Presentation: HTML5 And Fastest Encoding
Bitmovin Inc
Lessons Learned Deploying Modern Cloud Systems in Highly Regulated Environments
Lessons Learned Deploying Modern Cloud Systems in Highly Regulated Environments
Puma Security, LLC
Drupal CDN integration: easier, more flexible and faster!
Drupal CDN integration: easier, more flexible and faster!
Wim Leers
Mais procurados
(20)
Future of CDN - Next 10 Years - Ahmet Ozalp, Akamai Technologies - DigiWorld ...
Future of CDN - Next 10 Years - Ahmet Ozalp, Akamai Technologies - DigiWorld ...
Edge 2016 keeping tls secure
Edge 2016 keeping tls secure
Open source Cloud Automation Platform
Open source Cloud Automation Platform
Metrics, metrics everywhere (but where the heck do you start?)
Metrics, metrics everywhere (but where the heck do you start?)
Incapsula: How to Increase SaaS Websites’ Uptime and Accelerate Performance
Incapsula: How to Increase SaaS Websites’ Uptime and Accelerate Performance
Gwava gwava6
Gwava gwava6
A Modern Approach to Performance Monitoring
A Modern Approach to Performance Monitoring
Configs, Configs, Everywhere! (Actually, Let's Simplify All Those Configs)
Configs, Configs, Everywhere! (Actually, Let's Simplify All Those Configs)
VMware 2V0-21.20 Practice Test
VMware 2V0-21.20 Practice Test
Veeam Availability Suite version 10
Veeam Availability Suite version 10
Belgrade when its just too slow
Belgrade when its just too slow
Qa fest kiev_when its just too slow
Qa fest kiev_when its just too slow
Speed Up WordPress Websites - Part 1 - WordPress Cairo Meetup
Speed Up WordPress Websites - Part 1 - WordPress Cairo Meetup
Hacking Web Performance
Hacking Web Performance
Cloud Security: Attacking The Metadata Service
Cloud Security: Attacking The Metadata Service
Metrics, Metrics Everywhere (but where the heck do you start?)
Metrics, Metrics Everywhere (but where the heck do you start?)
Cloud based Performance Testing
Cloud based Performance Testing
IBC Content Everywhere Hub Presentation: HTML5 And Fastest Encoding
IBC Content Everywhere Hub Presentation: HTML5 And Fastest Encoding
Lessons Learned Deploying Modern Cloud Systems in Highly Regulated Environments
Lessons Learned Deploying Modern Cloud Systems in Highly Regulated Environments
Drupal CDN integration: easier, more flexible and faster!
Drupal CDN integration: easier, more flexible and faster!
Semelhante a Akamai Korea - Tech Day (2015/03/11) HTTP/2
Third Party Performance (Velocity, 2014)
Third Party Performance (Velocity, 2014)
Guy Podjarny
DIY Website Performance - Akamai Toronto Tech Day 2015
DIY Website Performance - Akamai Toronto Tech Day 2015
Desmond Tam
Tom uk soti_final_without video.4.21.15
Tom uk soti_final_without video.4.21.15
Liz Bradley
Third party-performance (Airbnb Nerds, Nov 2013)
Third party-performance (Airbnb Nerds, Nov 2013)
Guy Podjarny
Networks, Networks Everywhere, And Not A Packet To Drink
Networks, Networks Everywhere, And Not A Packet To Drink
ReadWrite
Chicago Tech Day Jan 2015: Foundry - HTTP2
Chicago Tech Day Jan 2015: Foundry - HTTP2
Akamai Technologies
Proven strategy for testing pw as aus-agile_testers
Proven strategy for testing pw as aus-agile_testers
Perfecto Mobile
Embarking on MuleSoft Automation Journey via RPA, Composer and Flex Gateway
Embarking on MuleSoft Automation Journey via RPA, Composer and Flex Gateway
Eva Mave Ng
2022-221021003409-5f494fb1.pdf
2022-221021003409-5f494fb1.pdf
Srinivasa771031
Great Expectations - Dr. Tom Leighton, Akamai
Great Expectations - Dr. Tom Leighton, Akamai
Akamai Technologies
UI5 with Akamai - Introduction to the Content Delivery Network
UI5 with Akamai - Introduction to the Content Delivery Network
Gokul Anand E, PMP®
[RakutenTechConf2013] [E-2] HTML5 in Rakuten
[RakutenTechConf2013] [E-2] HTML5 in Rakuten
Rakuten Group, Inc.
Holiday Retail Readiness: Preparing For Peak
Holiday Retail Readiness: Preparing For Peak
G3 Communications
게임 서비스를 위한 클라우드 네트워크 활용
게임 서비스를 위한 클라우드 네트워크 활용
Seung Heun Noh
Containerising the Mule Runtime with Kubernetes & From Zero to Batch : MuleS...
Containerising the Mule Runtime with Kubernetes & From Zero to Batch : MuleS...
Angel Alberici
DESAYUNO DE TRABAJO AKAMAI
DESAYUNO DE TRABAJO AKAMAI
Cristian Garcia G.
Singapore MuleSoft Meetup - 23 Nov 2022
Singapore MuleSoft Meetup - 23 Nov 2022
Royston Lobo
Akamai: From Theory to Practice
Akamai: From Theory to Practice
Liz Bradley
Third Party Performance
Third Party Performance
Guy Podjarny
Client-Side Performance Testing
Client-Side Performance Testing
Anand Bagmar
Semelhante a Akamai Korea - Tech Day (2015/03/11) HTTP/2
(20)
Third Party Performance (Velocity, 2014)
Third Party Performance (Velocity, 2014)
DIY Website Performance - Akamai Toronto Tech Day 2015
DIY Website Performance - Akamai Toronto Tech Day 2015
Tom uk soti_final_without video.4.21.15
Tom uk soti_final_without video.4.21.15
Third party-performance (Airbnb Nerds, Nov 2013)
Third party-performance (Airbnb Nerds, Nov 2013)
Networks, Networks Everywhere, And Not A Packet To Drink
Networks, Networks Everywhere, And Not A Packet To Drink
Chicago Tech Day Jan 2015: Foundry - HTTP2
Chicago Tech Day Jan 2015: Foundry - HTTP2
Proven strategy for testing pw as aus-agile_testers
Proven strategy for testing pw as aus-agile_testers
Embarking on MuleSoft Automation Journey via RPA, Composer and Flex Gateway
Embarking on MuleSoft Automation Journey via RPA, Composer and Flex Gateway
2022-221021003409-5f494fb1.pdf
2022-221021003409-5f494fb1.pdf
Great Expectations - Dr. Tom Leighton, Akamai
Great Expectations - Dr. Tom Leighton, Akamai
UI5 with Akamai - Introduction to the Content Delivery Network
UI5 with Akamai - Introduction to the Content Delivery Network
[RakutenTechConf2013] [E-2] HTML5 in Rakuten
[RakutenTechConf2013] [E-2] HTML5 in Rakuten
Holiday Retail Readiness: Preparing For Peak
Holiday Retail Readiness: Preparing For Peak
게임 서비스를 위한 클라우드 네트워크 활용
게임 서비스를 위한 클라우드 네트워크 활용
Containerising the Mule Runtime with Kubernetes & From Zero to Batch : MuleS...
Containerising the Mule Runtime with Kubernetes & From Zero to Batch : MuleS...
DESAYUNO DE TRABAJO AKAMAI
DESAYUNO DE TRABAJO AKAMAI
Singapore MuleSoft Meetup - 23 Nov 2022
Singapore MuleSoft Meetup - 23 Nov 2022
Akamai: From Theory to Practice
Akamai: From Theory to Practice
Third Party Performance
Third Party Performance
Client-Side Performance Testing
Client-Side Performance Testing
Mais de SangJin Kang
웹에 빠른 날개를 달아주는 웹 성능 향상 이야기
웹에 빠른 날개를 달아주는 웹 성능 향상 이야기
SangJin Kang
Web Performance Optimization with HTTP/3
Web Performance Optimization with HTTP/3
SangJin Kang
How to Replicate PostgreSQL Database
How to Replicate PostgreSQL Database
SangJin Kang
Scalability strategies for cloud based system architecture
Scalability strategies for cloud based system architecture
SangJin Kang
HTTP/3 시대의 웹 성능 최적화 기술 이해하기
HTTP/3 시대의 웹 성능 최적화 기술 이해하기
SangJin Kang
수요자 중심의 클라우드 운영 및 전략 (CIO Summit 2019)
수요자 중심의 클라우드 운영 및 전략 (CIO Summit 2019)
SangJin Kang
How to develop and localize Xbox 360 titles
How to develop and localize Xbox 360 titles
SangJin Kang
HTTP 프로토콜의 이해와 활용
HTTP 프로토콜의 이해와 활용
SangJin Kang
HTTP/2와 웹 성능 최적화 방안
HTTP/2와 웹 성능 최적화 방안
SangJin Kang
HTML5 for web app. development
HTML5 for web app. development
SangJin Kang
Agile - SCRUM을 통한 개발관리
Agile - SCRUM을 통한 개발관리
SangJin Kang
XNA2.0 Network Programming
XNA2.0 Network Programming
SangJin Kang
XNA Introduction
XNA Introduction
SangJin Kang
Mais de SangJin Kang
(13)
웹에 빠른 날개를 달아주는 웹 성능 향상 이야기
웹에 빠른 날개를 달아주는 웹 성능 향상 이야기
Web Performance Optimization with HTTP/3
Web Performance Optimization with HTTP/3
How to Replicate PostgreSQL Database
How to Replicate PostgreSQL Database
Scalability strategies for cloud based system architecture
Scalability strategies for cloud based system architecture
HTTP/3 시대의 웹 성능 최적화 기술 이해하기
HTTP/3 시대의 웹 성능 최적화 기술 이해하기
수요자 중심의 클라우드 운영 및 전략 (CIO Summit 2019)
수요자 중심의 클라우드 운영 및 전략 (CIO Summit 2019)
How to develop and localize Xbox 360 titles
How to develop and localize Xbox 360 titles
HTTP 프로토콜의 이해와 활용
HTTP 프로토콜의 이해와 활용
HTTP/2와 웹 성능 최적화 방안
HTTP/2와 웹 성능 최적화 방안
HTML5 for web app. development
HTML5 for web app. development
Agile - SCRUM을 통한 개발관리
Agile - SCRUM을 통한 개발관리
XNA2.0 Network Programming
XNA2.0 Network Programming
XNA Introduction
XNA Introduction
Último
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
lesteraporado16
Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024
Shubham Pant
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Roxana Stingu
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
Shreedeep Rayamajhi
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
mchristianalwyn
Zero-day Vulnerabilities
Zero-day Vulnerabilities
alihassaah1994
Bio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptx
naveenithkrishnan
Computer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a Website
Mavein
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
Jan Löffler
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
APNIC
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
edrianrheine
Presentation2.pptx - JoyPress Wordpress
Presentation2.pptx - JoyPress Wordpress
ssuser166378
Último
(12)
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
Zero-day Vulnerabilities
Zero-day Vulnerabilities
Bio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptx
Computer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a Website
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
Presentation2.pptx - JoyPress Wordpress
Presentation2.pptx - JoyPress Wordpress
Akamai Korea - Tech Day (2015/03/11) HTTP/2
1.
©2015 AkamaiFASTER FORWARDTMConfidential 2015.02.23
2.
강상진
3.
(sangjinn@gmail.com)
4.
http://brandonk.tistory.com
5.
6.
7.
8.
GET
9.
/
10.
HTTP/2
11.
12.
User-Agent:
13.
Akamai
14.
Korea
15.
-
16.
Tech
17.
Day
18.
19.
Host:
20.
www.akamai.co.kr
21.
22.
Accept:
23.
Everyone
24.
....
25.
26.
Content-Type:
27.
Open
28.
Seminar
29.
30.
Date:
31.
Wed,
32.
11
33.
Mar
34.
2015
35.
16:00:00
36.
KST
37.
38.
Expires:
39.
Wed,
40.
11
41.
Mar
42.
2015
43.
18:00:00
44.
KST
45.
46.
Connection:
47.
Keep-Alive
48.
49.
Set-Cookie:
50.
Speaker=Brandon
51.
Kang;
52.
Role=Sr.
53.
TPM
54.
Lead
55.
56.
57.
©2015
58.
AKAMAI
59.
60.
|
61.
62.
FASTER
63.
FORWARDTM
64.
강연자
65.
소개
66.
Brandon Kang 前) Samsung
SDS 솔루션
67.
개발센터
68.
선임
69.
개발자 前) Microsoft Korea
RD 책임
70.
연구원 前)
71.
한국콘텐트진흥원
72.
글로벌
73.
창업지원
74.
프로그램
75.
심사위원 前)
76.
한국게임개발자협회(KGDA) 게임
77.
개발
78.
멘토 미래창조과학부
79.
Software Maestro 개발
80.
분야
81.
멘토 아카마이
82.
한국
83.
법인
84.
Sr. Technical Project
Manager Lead 집필/번역 IT 트렌드
85.
/ 웹
86.
프로그래밍
87.
/ XML 웹
88.
서비스
89.
/
90.
모바일
91.
어플
92.
개발
93.
/
94.
게임
95.
개발
96.
등
97.
11권 강연/강의 KGC(Korea Game Conference),
MSDN, KOBA, Icon, e-Fun 등의
98.
기술
99.
세미나
100.
강연/강의
101.
©2015
102.
AKAMAI
103.
104.
|
105.
106.
FASTER
107.
FORWARDTM
108.
109.
110.
왜
111.
HTTP/2인가?
112.
113.
©2015
114.
AKAMAI
115.
116.
|
117.
118.
FASTER
119.
FORWARDTM
120.
121.
122.
웹은
123.
진화
124.
하였다.
125.
그리고..
126.
계속
127.
128.
진화하고
129.
있다…⋯
130.
131.
©2015
132.
AKAMAI
133.
134.
|
135.
136.
FASTER
137.
FORWARDTM
138.
139.
140.
141.
©2015
142.
AKAMAI
143.
144.
|
145.
146.
FASTER
147.
FORWARDTM
148.
149.
150.
모바일
151.
디바이스
152.
증가
153.
154.
©2015
155.
AKAMAI
156.
157.
|
158.
159.
FASTER
160.
FORWARDTM
161.
162.
163.
웹
164.
성능이
165.
MONEY?
166.
167.
©2015
168.
AKAMAI
169.
170.
|
171.
172.
FASTER
173.
FORWARDTM
174.
175.
176.
HTTP1.1의
177.
단점
178.
179.
©2015
180.
AKAMAI
181.
182.
|
183.
184.
FASTER
185.
FORWARDTM
186.
Head
187.
of
188.
Line
189.
Blocking
190.
(특정
191.
응답의
192.
지연)
193.
Client Server Time ?
194.
©2015
195.
AKAMAI
196.
197.
|
198.
199.
FASTER
200.
FORWARDTM
201.
Head
202.
of
203.
Line
204.
Blocking
205.
(특정
206.
응답의
207.
지연)
208.
HTML
209.
응답
210.
이전에
211.
이미지는
212.
전달되지
213.
않음
214.
215.
©2015
216.
AKAMAI
217.
218.
|
219.
220.
FASTER
221.
FORWARDTM
222.
Multiple
223.
Connections
224.
(TCP
225.
handshake의
226.
반복)
227.
228.
©2015
229.
AKAMAI
230.
231.
|
232.
233.
FASTER
234.
FORWARDTM
235.
GET / HTTP/1.1! Host:
www.akamai.com! User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 ! Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8! DNT: 1! Accept-Language: en-us! Accept-Encoding: gzip, deflate! Cookie: uaid=uaid%3DVdhk5W6sexG-_Y7ZBeQFa3cq7yMQ%26_now%3D1325204464%26_slt%3Ds_LCLVpU! Connection: keep-alive 525
236.
Bytes
237.
무거운
238.
헤더
239.
구조
240.
(HTTP
241.
메시지의
242.
한계)
243.
244.
©2015
245.
AKAMAI
246.
247.
|
248.
249.
FASTER
250.
FORWARDTM
251.
무거운
252.
헤더
253.
구조
254.
(HTTP
255.
메시지의
256.
한계)
257.
GET /assets/dist/js/etsy.recent-searches.20121001205006.js HTTP/1.1! Host:
www.akamai.com! User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14! Accept: */*! DNT: 1! Referer: http://www.akamai.com/! Accept-Language: en-us! Accept-Encoding: gzip, deflate! Cookie: autosuggest_split=1;etala=111461200.1476767743.1349274889.1349274889.1349274889.1.0; ! Connection: keep-alive 226
258.
New
259.
Bytes;
260.
690
261.
Total
262.
263.
©2015
264.
AKAMAI
265.
266.
|
267.
268.
FASTER
269.
FORWARDTM
270.
무거운
271.
헤더
272.
구조
273.
(HTTP
274.
메시지의
275.
한계)
276.
GET /assets/dist/js/jquery.appear.20121001205006.js HTTP/1.1! Host:
www.akamai.com! User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML! Accept: */*! DNT: 1! Referer: http://www.akamai.com/! Accept-Language: en-us! Accept-Encoding: gzip, deflate! Cookie: autosuggest_split=1;etala=111461200.1476767743.1349274889.1349274889.1349274889.1.0; ! Connection: keep-alive 14
277.
New
278.
Bytes;
279.
683
280.
Total
281.
282.
©2015
283.
AKAMAI
284.
285.
|
286.
287.
FASTER
288.
FORWARDTM
289.
무거운
290.
헤더
291.
구조
292.
(HTTP
293.
메시지의
294.
한계)
295.
GET /assets/dist/js/bootstrap/username-suggester.20121001205006.js HTTP/1.1! Host:
www.akamai.com! User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML! Accept: */*! DNT: 1! Referer: http://www.akamai.com/! Accept-Language: en-us! Accept-Encoding: gzip, deflate! Cookie: autosuggest_split=1;etala=111461200.1476767743.1349274889.1349274889.1349274889.1.0; Connection: keep-alive! 28
296.
New
297.
Bytes;
298.
698
299.
Total
300.
301.
©2015
302.
AKAMAI
303.
304.
|
305.
306.
FASTER
307.
FORWARDTM
308.
무거운
309.
헤더
310.
구조
311.
(HTTP
312.
메시지의
313.
한계)
314.
4개의
315.
요청
316.
동안…⋯.
317.
• 모두
318.
2596
319.
바이트
320.
전송
321.
• ~3개의
322.
패킷
323.
• 중복
324.
헤더
325.
1797
326.
바이트
327.
(전체
328.
70%
329.
)
330.
• 계속
331.
따라붙는
332.
쿠키…⋯
333.
(이것
334.
떼어낼
335.
수
336.
없나?)
337.
338.
©2015
339.
AKAMAI
340.
341.
|
342.
343.
FASTER
344.
FORWARDTM
345.
무거운
346.
헤더
347.
구조
348.
(HTTP
349.
메시지의
350.
한계)
351.
서버
352.
전송량:
353.
914
354.
B
355.
실제
356.
콘텐트:
357.
57
358.
B
359.
15배의
360.
헤더
361.
전송
362.
363.
©2015
364.
AKAMAI
365.
366.
|
367.
368.
FASTER
369.
FORWARDTM
370.
눈물겨운
371.
노력
372.
–
373.
Image
374.
Sprite
375.
(분할
376.
이미지
377.
사용)
378.
379.
©2015
380.
AKAMAI
381.
382.
|
383.
384.
FASTER
385.
FORWARDTM
386.
눈물겨운
387.
노력
388.
–
389.
Inline
390.
Script
391.
(스크립트
392.
병합)
393.
394.
©2015
395.
AKAMAI
396.
397.
|
398.
399.
FASTER
400.
FORWARDTM
401.
눈물겨운
402.
노력
403.
–
404.
Domain
405.
Sharding
406.
(도메인
407.
분할을
408.
통한
409.
병렬
410.
호출)
411.
412.
©2015
413.
AKAMAI
414.
415.
|
416.
417.
FASTER
418.
FORWARDTM
419.
눈물겨운
420.
노력
421.
–
422.
Script
423.
Minimization
424.
(스크립트
425.
최소화)
426.
427.
©2015
428.
AKAMAI
429.
430.
|
431.
432.
FASTER
433.
FORWARDTM
434.
저기요…⋯
435.
웹
436.
콘텐트
437.
수정은
438.
너무
439.
힘들어요…⋯
440.
프로토콜
441.
단에서
442.
수정하면
443.
안돼요???
444.
S사
445.
2015년
446.
대졸신입
447.
사원
448.
배**
449.
450.
전산학과
451.
졸업,
452.
24세.
453.
초급
454.
웹
455.
개발자
456.
457.
©2015
458.
AKAMAI
459.
460.
|
461.
462.
FASTER
463.
FORWARDTM
464.
465.
©2015
466.
AKAMAI
467.
468.
|
469.
470.
FASTER
471.
FORWARDTM
472.
HTTP
473.
• HTTP
474.
0.9
475.
-
476.
HTTP의
477.
탄생
478.
팀
479.
버너스리가
480.
최초에
481.
웹을
482.
발명했을
483.
때
484.
사용하던
485.
프로토콜
486.
현재의
487.
HTTP와
488.
다르게
489.
헤더가
490.
없으며,
491.
GET
492.
메소드만
493.
있음.
494.
495.
496.
• HTTP
497.
1.0
498.
-
499.
HTTP
500.
최초의
501.
표준화
502.
IETF
503.
에서
504.
표준화하여
505.
1993년에
506.
Draft
507.
공개후,
508.
509.
1996년에
510.
최종
511.
버전(RFC
512.
1945),
513.
헤더의
514.
도입,
515.
GET
516.
이외의
517.
518.
타
519.
메서드
520.
추가
521.
522.
523.
©2015
524.
AKAMAI
525.
526.
|
527.
528.
FASTER
529.
FORWARDTM
530.
HTTP
531.
532.
• HTTP
533.
1.1
534.
-
535.
HTTP의
536.
완성
537.
1997년
538.
RFC
539.
2068
540.
에서
541.
개정하여
542.
1999년
543.
RFC
544.
2616
545.
발행.
546.
547.
현재의
548.
1.1
549.
스펙,
550.
채널전송,
551.
Accept
552.
헤더에
553.
의한
554.
content
555.
negotiation,
556.
cache-control,
557.
Keep-Alive
558.
등
559.
실용적인
560.
헤더들의
561.
대거
562.
추가
563.
564.
• SPDY
565.
-
566.
좀더
567.
빠른
568.
웹을
569.
위한
570.
실험적인
571.
프로토콜
572.
구글이
573.
제안하는
574.
HTTP
575.
프로토콜의
576.
개선안.
577.
578.
SSL/헤더
579.
압축/다중
580.
스트림/요청
581.
우선
582.
순위
583.
등
584.
585.
*
586.
2014년
587.
2월,
588.
SPDY
589.
기반의
590.
HTTP/2
591.
발표
592.
593.
©2015
594.
AKAMAI
595.
596.
|
597.
598.
FASTER
599.
FORWARDTM
600.
HTTP
601.
602.
603.
...
604.
605.
606.
607.
608.
HTTP/0.9
609.
1996/
610.
5
611.
HTTP/1.0
612.
(RFC
613.
1945)
614.
1997/
615.
1
616.
HTTP/1.1
617.
(RFC
618.
2068)
619.
2009/11
620.
SPDY/1
621.
...
622.
2011/
623.
9
624.
WebSocket(RFC
625.
6455)
626.
2012/
627.
8
628.
HTTP/2.0
629.
start
630.
2012/11
631.
HTTP/2.0
632.
(draft-00)
633.
2013/
634.
7
635.
HTTP/2.0
636.
(draft-04)
637.
2013/
638.
8
639.
interop
640.
testing
641.
2013/
642.
8
643.
HTTP/2.0
644.
(draft-05)
645.
…⋯
646.
647.
©2015
648.
AKAMAI
649.
650.
|
651.
652.
FASTER
653.
FORWARDTM
654.
HTTP/2
655.
• 1999년
656.
발표된
657.
HTTP1.1(RFC2616)
658.
이후,
659.
16년만의
660.
정식
661.
업데이트
662.
• IETF(Internet
663.
Engineering
664.
Task
665.
Force)
666.
워킹
667.
그룹이,
668.
Google이
669.
제안 한
670.
SPDY을
671.
모태로
672.
개발하여,
673.
2014년
674.
12월
675.
표준
676.
기술로
677.
승인
678.
요청
679.
• IESG(Internet
680.
Engineering
681.
Steering
682.
Group)에서
683.
2015년
684.
2월
685.
17일,
686.
687.
이
688.
제안을
689.
승인하고
690.
proposed
691.
standard로
692.
발표
693.
• 정식
694.
RFC
695.
진행
696.
중
697.
698.
기술적
699.
의미
700.
• HTTP1.1의
701.
고질적
702.
문제인
703.
head-of-line-breaking을
704.
해결함
705.
• HTTP1.1의
706.
Keep-Alive를
707.
Parallel
708.
connection으로
709.
승화시킴;;;
710.
711.
©2015
712.
AKAMAI
713.
714.
|
715.
716.
FASTER
717.
FORWARDTM
718.
HTTP/2
719.
프로토콜
720.
• SSL
721.
Handshake
722.
for
723.
HTTPS
724.
(NPN
725.
–
726.
SPDY,
727.
ALPN
728.
–
729.
HTTP/2)
730.
• TLS
731.
-
732.
SPDY
733.
에선
734.
MUST,
735.
HTTP/2에선
736.
옵션
737.
• DATA
738.
및
739.
Header
740.
모두
741.
압축(Compression)
742.
Application
743.
(HTTP/2)
744.
Session
745.
(TLS,
746.
optional)
747.
Transport
748.
(TCP)
749.
Network
750.
(IP)
751.
POST
752.
/upload
753.
HTTP/1.1
754.
Host:
755.
www.akamai.com
756.
Content-Type:
757.
application/json
758.
Content-Length:
759.
15
760.
761.
{“msg”:”Hello
762.
World!”}
763.
HEADERS
764.
frame
765.
DATA
766.
frame
767.
Binary
768.
Framing
769.
HTTP/2
770.
HTTP
771.
1.1
772.
773.
©2015
774.
AKAMAI
775.
776.
|
777.
778.
FASTER
779.
FORWARDTM
780.
HTTP/2
781.
스트림
782.
• Stream은
783.
HTTP1.X의
784.
Req/Res와
785.
같은
786.
HEADER/DATA의
787.
조합
788.
• HEADER와
789.
DATA는
790.
Frame이라는
791.
구조를
792.
가짐
793.
• 하나의
794.
Connection이
795.
Client
796.
-
797.
798.
Server
799.
간
800.
유지
801.
• 헤더와
802.
데이터(BODY)는
803.
스트림을
804.
통해
805.
전달
806.
Stream
807.
1
808.
DATA
809.
Stream
810.
3
811.
HEADERS
812.
Stream
813.
3
814.
DATA
815.
Stream
816.
1
817.
DATA
818.
…⋯…⋯…⋯.
819.
Stream
820.
5
821.
DATA
822.
823.
©2015
824.
AKAMAI
825.
826.
|
827.
828.
FASTER
829.
FORWARDTM
830.
Server
831.
Push
832.
Stream
833.
4
834.
Frame
835.
1
836.
…⋯…⋯…⋯…⋯
837.
Stream
838.
1
839.
Frame
840.
n
841.
Stream
842.
4
843.
promise
844.
Stream
845.
2
846.
promise
847.
Stream
848.
1
849.
Frame
850.
2
851.
Stream
852.
1:
853.
/index.html
854.
855.
856.
(Client
857.
요청)
858.
Stream
859.
2:
860.
/jsscript.js
861.
862.
863.
864.
865.
866.
(push
867.
promise)
868.
Stream
869.
4:
870.
/cssstyle.css
871.
872.
873.
(push
874.
promise)
875.
• 서버는
876.
다음
877.
요청이
878.
오기전,
879.
응답을
880.
미리
881.
줄
882.
수
883.
있음
884.
(Push
885.
Promise)
886.
• 현재
887.
아카마이가
888.
제공하는
889.
Prefetch와
890.
유사한
891.
기능
892.
• 전달된
893.
콘텐트는
894.
브라우져
895.
캐시를
896.
통해
897.
재사용
898.
가능
899.
900.
©2015
901.
AKAMAI
902.
903.
|
904.
905.
FASTER
906.
FORWARDTM
907.
중복
908.
헤더
909.
제거
910.
및
911.
압축
912.
:method
913.
GET
914.
:scheme
915.
https
916.
:host
917.
akamai.com
918.
:path
919.
/index
920.
accept
921.
Image/jpeg
922.
User-agent
923.
Mozilla/5.0..
924.
:method
925.
GET
926.
:scheme
927.
https
928.
:host
929.
akamai.com
930.
:path
931.
/new
932.
accept
933.
Image/jpeg
934.
User-agent
935.
Mozilla/5.0..
936.
요청
937.
#1 요청
938.
#2 HEADERS
939.
Frame
940.
(Stream
941.
1)
942.
HEADERS
943.
Frame
944.
(Stream
945.
3)
946.
:method:
947.
GET
948.
:scheme:
949.
https
950.
:host:
951.
akamai.com
952.
:path:
953.
/index
954.
:accept:
955.
image/jpeg
956.
User-agent:
957.
Mozilla/5.0…⋯
958.
:path:
959.
/new
960.
• 중복
961.
헤더는
962.
다음
963.
요청에서
964.
제거
965.
• 나머지
966.
헤더는
967.
압축
968.
969.
©2015
970.
AKAMAI
971.
972.
|
973.
974.
FASTER
975.
FORWARDTM
976.
Pipelining의
977.
개선
978.
–
979.
HOL
980.
제거
981.
Client
982.
Server
983.
Time
984.
Client
985.
Server
986.
Time
987.
빠른
988.
응답
989.
990.
©2015
991.
AKAMAI
992.
993.
|
994.
995.
FASTER
996.
FORWARDTM
997.
응답
998.
우선
999.
순위화
1000.
(Prioritization)
1001.
Client는
1002.
어떤
1003.
응답이
1004.
제일
1005.
중요한지,
1006.
우선
1007.
순위를
1008.
알려주고,
1009.
서버는
1010.
이에
1011.
응답할
1012.
수
1013.
있음
1014.
1015.
예)
1016.
1017.
이미지
1018.
1019.
처리를
1020.
위해
1021.
CSS를
1022.
이미지보다
1023.
먼저…⋯..
1024.
Time Client
1025.
Server
1026.
1027.
©2015
1028.
AKAMAI
1029.
1030.
|
1031.
1032.
FASTER
1033.
FORWARDTM
1034.
HTTP1.X
1035.
vs.
1036.
HTTP/2
1037.
1038.
©2015
1039.
AKAMAI
1040.
1041.
|
1042.
1043.
FASTER
1044.
FORWARDTM
1045.
HTTP1.X
1046.
vs.
1047.
HTTP/2
1048.
1049.
©2015
1050.
AKAMAI
1051.
1052.
|
1053.
1054.
FASTER
1055.
FORWARDTM
1056.
결론…⋯.
1057.
평균
1058.
로딩
1059.
속도
1060.
10~25%
1061.
향상.
1062.
일반적인
1063.
FEO
1064.
요소
1065.
불필요
1066.
1067.
1068.
1069.
1070.
©2015
1071.
AKAMAI
1072.
1073.
|
1074.
1075.
FASTER
1076.
FORWARDTM
1077.
1078.
1079.
아카마이에선
1080.
HTTP/2
1081.
1082.
지원하나요?
1083.
1084.
©2015
1085.
AKAMAI
1086.
1087.
|
1088.
1089.
FASTER
1090.
FORWARDTM
1091.
1092.
1093.
1094.
©2015
1095.
AKAMAI
1096.
1097.
|
1098.
1099.
FASTER
1100.
FORWARDTM
1101.
IETF/아카마이
1102.
로드맵
1103.
2009
1104.
2011
1105.
2013
1106.
Google
1107.
announces
1108.
SPDY/2
1109.
SPDY
1110.
1111.
at
1112.
IETF80
1113.
Firefox
1114.
ships
1115.
SPDY
1116.
Call
1117.
for
1118.
HTTP/2
1119.
proposals
1120.
HTTPbis
1121.
rechartered
1122.
for
1123.
HTTP/2
1124.
Akamai
1125.
announces
1126.
SPDY
1127.
support
1128.
1129.
©2015
1130.
AKAMAI
1131.
1132.
|
1133.
1134.
FASTER
1135.
FORWARDTM
1136.
IETF/아카마이
1137.
로드맵
1138.
2013 2014 Draft-00 Draft-04 Draft-06 Draft-09
Draft-12 Draft-14 Draft-16 2015
1139.
©2015
1140.
AKAMAI
1141.
1142.
|
1143.
1144.
FASTER
1145.
FORWARDTM
1146.
IETF/아카마이
1147.
로드맵
1148.
BETA CHANNEL LAUNCH GENERAL AVAILABILITY HTTP/2-ENABLED FEATURES Opt-in • Edge
to client only • Secure network only • Web Performance products Opt-out • Edge to client only • Likely additional networks • Likely additional product lines TBD • Candidate examples: - Predictive Server Push - Smart Stream Priorities - HTTP/2 to origin Expected Chrome, Firefox, and IE support 2H2014 2H2015 1H2016
1149.
©2015
1150.
AKAMAI
1151.
1152.
|
1153.
1154.
FASTER
1155.
FORWARDTM
1156.
FAQs
1157.
• 다시
1158.
한번
1159.
HTTP/2
1160.
새로운
1161.
기능을
1162.
요약해주세요.
1163.
1164.
Multiplexing:
1165.
1166.
복수개의
1167.
요청이
1168.
하나의
1169.
TCP
1170.
connection으로
1171.
가능,
1172.
응답은
1173.
순서에
1174.
상관없이
1175.
stream으로
1176.
받습니다.
1177.
기존의
1178.
Connection
1179.
Keep-Alive,
1180.
Pipelining의
1181.
개선이라
1182.
보시면
1183.
됩니다.
1184.
1185.
중복
1186.
헤더
1187.
제거
1188.
및
1189.
헤더
1190.
압축:
1191.
1192.
같은
1193.
헤더를
1194.
제거하여
1195.
헤더
1196.
크기를
1197.
Huffman
1198.
coding
1199.
방식으로
1200.
나머지
1201.
헤더 들도
1202.
압축하여
1203.
전반적인
1204.
헤더
1205.
크기를
1206.
줄입니다
1207.
1208.
©2015
1209.
AKAMAI
1210.
1211.
|
1212.
1213.
FASTER
1214.
FORWARDTM
1215.
FAQs
1216.
• 다시
1217.
한번
1218.
HTTP/2
1219.
새로운
1220.
기능을
1221.
요약해주세요.
1222.
1223.
스트림
1224.
우선
1225.
순위화:
1226.
클라이언트는
1227.
서버에게
1228.
어떤
1229.
콘텐트가
1230.
중요하여
1231.
먼저
1232.
받기를
1233.
원하는지에
1234.
대한
1235.
정보를
1236.
전달할
1237.
수
1238.
있습니다.
1239.
1240.
서버
1241.
푸시:
1242.
서버는
1243.
요청받지
1244.
않은
1245.
콘텐트라도
1246.
미리
1247.
클라이언트측에
1248.
전달할
1249.
수
1250.
있습니 다.
1251.
1252.
©2015
1253.
AKAMAI
1254.
1255.
|
1256.
1257.
FASTER
1258.
FORWARDTM
1259.
FAQs
1260.
• 아카마이는
1261.
어떻게
1262.
HTTP/2에
1263.
투자하고
1264.
있나요?
1265.
IETF
1266.
의장이며
1267.
HTTP/2를
1268.
설계한
1269.
Mark
1270.
Nottingham은
1271.
아카마이의
1272.
Principal
1273.
Architect
1274.
입니다.
1275.
아카마이는
1276.
HTTP(S)를
1277.
통해
1278.
모든
1279.
서비스를
1280.
수행하기에
1281.
HTTP/2의
1282.
리드로서
1283.
로드맵을
1284.
진행하고
1285.
있습니다.
1286.
1287.
• 왜
1288.
HTTP2.0이
1289.
아니라,
1290.
HTTP/2인가요?
1291.
IETF는
1292.
HTTP2.X
1293.
서브
1294.
버전이
1295.
없을
1296.
것이라고
1297.
공식적으로
1298.
발표
1299.
하였습니다.
1300.
1301.
• HTTP/2가
1302.
사용되면
1303.
SPDY는
1304.
어떻게
1305.
되는건가요?
1306.
SPDY를
1307.
기반으로
1308.
많은
1309.
요소들이
1310.
이미
1311.
HTTP/2에
1312.
적용되어
1313.
중복으로
1314.
1315.
필요
1316.
없습니다.
1317.
1318.
©2015
1319.
AKAMAI
1320.
1321.
|
1322.
1323.
FASTER
1324.
FORWARDTM
1325.
FAQs
1326.
• 현재
1327.
아카마이를
1328.
통해
1329.
서비스를
1330.
받고
1331.
있습니다.
1332.
1333.
HTTP/2는
1334.
언제
1335.
적용
1336.
가능할까요?
1337.
SPDY
1338.
베타는
1339.
언제든
1340.
가능,
Baixar agora