TL;DR
Instead of just hunting for "bots" based on identity, this paper proposes ranking web sessions by the actual damage they do to a cache—specifically, how many "victim" misses they cause by evicting useful data. Their method identifies a tiny fraction of traffic responsible for nearly half of all cache harm, much of which is completely missed by traditional bot labels.
What Problem Does This Paper Address?
Web caches are vital for e-commerce performance, reducing latency and origin server load. However, automated traffic (scrapers, crawlers) often disrupts "cache locality." They may evict objects that human shoppers need, leading to lower cache hit ratios (CHR) and sluggish site performance.
Existing bot defenses typically try to infer automation from User-Agent (UA) strings or navigation patterns. The authors argue this is the wrong target: identity is a poor proxy for consequence. A "good" bot might warm the cache by requesting popular items, while a "human-looking" scraper might be devastating by sweeping through cold, unpopular URIs. This paper shifts the focus from who a client is to what harm they cause to other users.
Methods
The authors introduce a consequence-grounded ranking pipeline that operates retrospectively on server logs:
- Attribution: Using a single chronological replay of logs, they attribute every "victim miss" (a miss by a protected human shopper on a previously cached object) to the specific session whose insertion last evicted that object.
- Behavioral Modeling: They train a gradient-boosted regressor (HistGBM) to predict this attributed harm using 20 behavioral features (e.g., request volume, URI rarity, and timing). Crucially, they exclude UA strings and identity tags to ensure the model learns harmful behavior rather than just labeling known bots.
- Retrospective Bypass Simulation: To evaluate the impact, they simulate "bypassing" the top-ranked harmful sessions—sending their requests directly to the origin without letting them read from or write to the shared cache—and measure the resulting CHR improvement for the remaining human shoppers.
Datasets
- EClog: A primary 183-day trace from a Polish e-commerce store containing ~12.7 million replayed requests.
- Zanbil: A secondary 5-day trace used to verify that the observed phenomena (like harm concentration) generalize across different stores.
- Synthetic Personas: Three types of simulated attackers (scrapers and monitors) were interleaved with real traffic for controlled "stress tests" to validate that the attribution method correctly identifies known-harmful actors.
Key Insights and Ideas
- Harm is highly concentrated: Cache harm follows a steep power-law distribution. As shown in Figure 3, the top 1% of sessions in the EClog dataset were responsible for 48.8% of all attributed cache harm (Gini coefficient of 0.91). This means a very narrow, surgical intervention can have a massive impact.
- Bot labels are a leaky bucket: Traditional UA-based bot tags missed nearly half (49.1%) of the harm in the top 1% tier. Many high-harm sessions use browser-like UAs to evade detection.
- Attribution tracks reality: The authors validated their metric using a "leave-one-session-out" check. They found that their single-pass attribution score correlates strongly (Spearman $\rho = 0.80$) with the actual increase in human cache hits when that specific session is removed from the stream.
Key Results
- Efficiency: At a common request-volume target (20%), the proposed ranker achieved 93% of the CHR improvement of a UA-based baseline while selecting 47 times fewer sessions (3.6k vs 167k). This drastically reduces the "audit burden" for security teams.
- Robustness: The findings were consistent across different cache replacement policies (LRU, ARC, S3-FIFO) and across both the EClog and Zanbil datasets.
- Victim Safety: The ranker maintained a very low "victim bypass rate" of 0.18%, ensuring that legitimate human shoppers are rarely caught in the crossfire of cache-bypass interventions.
Limitations and Future Work
- Retrospective Scope: The current method is an offline audit tool. Adapting it for live, "prospective" use would require handling real-time model updates and using only past-looking features.
- Origin Egress: Bypassing the cache increases the load on the origin server. A production implementation would need "origin-aware budgets" to ensure that protecting the cache doesn't accidentally overwhelm the backend.
- Simplified Cache Model: The study uses a simplified URI-key application cache. Future work could incorporate more complex HTTP semantics like Time-to-Live (TTL) and
Varyheaders to better reflect real-world CDN environments.
Summary updated