We reported block working but usage time exceeded budget time

Royce Branning created a high priority On-Call Investigation CLE-1023 Block works but usage exceeds budget

Root caused. The domain responsible for most of the traffic in this case was a new domain. Proxy looked it up, found no activities for it, cached that result, then API marked it blockable but cache didn't block it • 221020 First Disney+ session starts. The iPad connects to vod-ftc-na-south-1.media.dssott.com The proxy looks the host up, finds no mapping, and caches [] for about 24 hours • 221042

/uploadIOSFlows

maps this host and it's a unique mapping to the Disney+ activity • 224215 The budget is hit and api sends the block to proxy. Proxy checks each open connection against its cache. The video host still reads [], so it doesn't cut it • 2242–2258 The video keeps streaming at 44 MB/min over the uncut connection. • Creating this PR to fix, need @Michael Landolfi's input

Oliver Hill - changed status to Done for ENG-550 Create browser blocking system that actually works