English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

HTTP response size is a well-known side channel attack. With the deploymentof HTTP/2.0, response size estimation attacks are generally dismissed with theargument that pipelining and response multiplexing prevent eavesdroppers fromfinding out response sizes. Yet the impact that pipelining and responsemultiplexing actually have in estimating HTTP response sizes has not beenadequately investigated. In this paper we set out to help understand the effectof pipelining and response multiplexing in estimating the size of web objectson the Internet. We conduct an experiment that collects HTTP response sizes andTLS record sizes from 10k popular web sites. We gather evidence on and discussreasons for the limited amount of pipelining and response multiplexing used onthe Internet today: only 29% of the HTTP2 web objects we observe are pipelinedand only 5% multiplexed. We also provide worst case results under differentattack assumptions and show how effective a simple model for estimatingresponse sizes from TLS record sizes can be. Our conclusion is that pipeliningand especially response multiplexing can yield, as expected, a perceivableincrease in relative object size estimation error yet the limited extent ofmultiplexing observed on the Internet today and the relative simplicity ofattacks to the current pipelining mechanisms hinder their ability to helpprevent web object size estimation.

Effect of Pipelining and Multiplexing in Estimating HTTP/2.0 Web Object Sizes