<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Effect of Pipelining and Multiplexing in Estimating HTTP/2.0 Web Object Sizes · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1707.00641/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1707.00641/feed.xml" rel="self" type="application/rss+xml" /><item><title>Effect of Pipelining and Multiplexing in Estimating HTTP/2.0 Web Object Sizes — mentioned by 1vuio0pswjnm7</title><link>https://news.ycombinator.com/item?id=31849366</link><guid isPermaLink="false">urn:hackerpapers:mention:1707.00641:31849366</guid><pubDate>Thu, 23 Jun 2022 14:10:31 GMT</pubDate><description>&lt;p&gt;&amp;quot;We also accounted for several resources that get loaded from different web servers due to the sub-queries performed when a website is requested. The set of all these IPs contacted is referred to as the Page Load Fingerprint (PLF) of the website.&amp;quot; This method is restricted to clients that automatically load resources and/or run Javascript, e.g., so-called &amp;quot;modern&amp;quot; browsers. It will not work with non-browser clients. For example, I make HTTP requests using TCP clients and HTTP generators. There is no automatic loading of resources nor Javascript support. Another example is CCBot, the Common…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1707.00641/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
