Cloudflare

Optimising Caching on Pwned Passwords (with Workers)

Aug 9, 2018Junade Ali
Optimising Caching on Pwned Passwords (with Workers)
SummaryAI, from the source post

This post details how Cloudflare's caching functionality was optimized for the Pwned Passwords API. It explains the use of custom cache key configurations to remove the 'Origin' header, which was causing duplicate caching due to varying origins. Additionally, it describes how Cloudflare Workers were used to standardize the casing of hash prefixes in API requests, preventing further cache duplication. The post also touches upon the role of Argo in providing tiered caching functionality.

More from the Cache Management trail