Is the Web HTTP/2 Yet?

Varvello, Matteo; Schomp, Kyle; Naylor, David; Blackburn, Jeremy; Finamore, Alessandro; Papagiannaki, Konstantina

doi:10.1007/978-3-319-30505-9_17

Cited by 56 publications

(49 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Varvello et al, 2016) periodically measures page load performance by loading real websites over real networks from their own origin servers. They observe that most websites using h2 also still use h1 best practices like embedding and sharding.…”

Section: Related Workmentioning

confidence: 99%

Concatenation, Embedding and Sharding: Do HTTP/1 Performance Best Practices Make Sense in HTTP/2?

Marx

Quax

Faes

et al. 2017

Proceedings of the 13th International Conference on Web Information Systems and Technologies

View full text Add to dashboard Cite

Abstract:Web page performance is becoming increasingly important for end users but also more difficult to provide by web developers, in part because of the limitations of the legacy HTTP/1 protocol. The new HTTP/2 protocol was designed with performance in mind, but existing work comparing its improvements to HTTP/1 often shows contradictory results. It is unclear for developers how to profit from HTTP/2 and whether current HTTP/1 best practices such as resource concatenation, resource embedding, and hostname sharding should still be used. In this work we introduce the Speeder framework, which uses established tools and software to easily and reproducibly test various setup permutations. We compare and discuss results over many parameters (e.g., network conditions, browsers, metrics), both from synthetic and realistic test cases. We find that in most non-extreme cases HTTP/2 is on a par with HTTP/1 and that most HTTP/1 best practices are applicable to HTTP/2. We show that situations in which HTTP/2 currently underperforms are mainly caused by inefficiencies in implementations, not due to shortcomings in the protocol itself.

show abstract

Section: Related Workmentioning

confidence: 99%

Concatenation, Embedding and Sharding: Do HTTP/1 Performance Best Practices Make Sense in HTTP/2?

Marx

Quax

Faes

et al. 2017

Proceedings of the 13th International Conference on Web Information Systems and Technologies

View full text Add to dashboard Cite

show abstract

“…The closest related work loads pages directly on the internet via various networks and shows more positive loadEventEnd results for h2 than our tests do, for example that 80% of pages on faster networks clearly benefit from h2 [26]. This percentage is lower on slower networks but there h2 typically also has a higher benefit.…”

Section: Resultsmentioning

confidence: 45%

“…[26] measures page load performance by loading real websites over real networks from their original origin servers. They find that most websites distribute their resources over multiple backend hosts and as such use h2 over multiple concurrent connections, which "makes h2 more resilient to packet loss and jitter".…”

Section: Introductionmentioning

confidence: 99%

Web Performance Characteristics of HTTP/2 and Comparison to HTTP/1.1

Marx

Wijnants

Quax

et al. 2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. The HTTP/1.1 protocol has long been a staple on the web, for both pages and apps. However, it has started to show its age, especially with regard to page load performance and the overhead it entails due to its use of multiple underlying connections. Its successor, the newly standardized HTTP/2, aims to improve the protocol's performance and reduce its overhead by (1) multiplexing multiple resources over a single TCP connection, (2) by using advanced prioritization strategies and by introducing new features such as (3) Server Push and (4) HPACK header compression. This work provides an in-depth overview of these four HTTP/2 performance aspects, discussing both synthetic and realistic experiments, to determine the gains HTTP/2 can provide in comparison to HTTP/1.1 in various settings. We find that the single multiplexed connection can actually become a significant performance bottleneck in poor network conditions with high packet loss and that HTTP/2 rarely improves much on HTTP/1.1, except in terms of reduced overhead. Prioritization strategies, Server Push and HPACK compression are found to have a relatively limited impact on web performance, but together with other observed HTTP/2 performance problems this could also be due to faulty current implementations, of which we have discovered various examples.

show abstract

“… Matteo et al [9] introduce the new feature in HTTP2 and addresses well-known problems with HTTP/1.1. The authors built a measurement platform that monitors HTTP/2 adoption and performance across the Alexa top 1 million websites on a daily basis for findings from an 11 month measurement campaign (November 2014 -October 2015).…”

Section: Related Workmentioning

confidence: 99%

Impact of Implementing HTTP/2 in Web Services

Darwish¹,

Abdelwahab²

2016

IJCA

View full text Add to dashboard Cite

HTTP/2 is the newest version of the HTTP1.1 protocol that was finalized in May 2015 and introduced as the IETF standard for web communication. HTTP/2 provides significant performance improvements by addressing well-known problems with HTTP/1.1 (e.g., head of line blocking and redundant headers) some of this features may have indirect impact in security. Also, HTTP/2 introduces new features like the default encryption which causes traffic hiding consequently affects a number of services (e.g., web Caching, Traffic classification).HTTP/2 may have some problems (vulnerabilities) like any new develop protocol lead to Denial of Service (DoS) attacks .The research try to figure out the pros and cons of the this new protocol version from different aspect specially security issues.

show abstract

Is the Web HTTP/2 Yet?

Cited by 56 publications

References 3 publications

Concatenation, Embedding and Sharding: Do HTTP/1 Performance Best Practices Make Sense in HTTP/2?

Concatenation, Embedding and Sharding: Do HTTP/1 Performance Best Practices Make Sense in HTTP/2?

Web Performance Characteristics of HTTP/2 and Comparison to HTTP/1.1

Impact of Implementing HTTP/2 in Web Services

Contact Info

Product

Resources

About