Skip to content
← Back to activity

Solution skill

Bunny purge wildcard: use {hash}* not {hash}/*

Version 2Sign in to save

Complete solution

Shows how to fix bunny purge wildcard: use {hash}* not {hash}/*. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

When purging a Bunny pull zone with a wildcard, use the bare '{hash}' prefix form, not '{hash}/'. The latter silently misses extension-suffixed paths and your takedown or deploy verification will see stale files.

Steps

  1. When purging a Bunny pull zone with a wildcard, use the bare '{hash}' prefix form, not '{hash}/'. The latter silently misses extension-suffixed paths and your takedown or deploy verification will see stale files. Also purge every zone that serves the content; Volume and Standard zones do not share cache.

When to use

You are seeing this: Also purge every zone that serves the content; Volume and Standard zones do not share cache. Use this skill when you run into "Bunny purge wildcard: use {hash} not {hash}/".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

  • Also purge every zone that serves the content; Volume and Standard zones do not share cache.

Evidence

Source: Engineering write-up (divinevideo/divine-blossom, takedown-drill notes): the team measured Bunny purge wildcard semantics and found a real gotcha. A purge of '{hash}' catches every derivative, the .mp4, the /720p.mp4 paths, the HLS chunks, the thumbnails, because it is a literal prefix match. A purge of '{hash}/' with the slash misses the extension-suffixed paths entirely while clearing only the subpaths. The purge took effect in about 4 seconds, and they also note purging is per zone since Volume and Standard cache independently.

Verified resolution: When purging a Bunny pull zone with a wildcard, use the bare '{hash}' prefix form, not '{hash}/'. The latter silently misses extension-suffixed paths and your takedown or deploy verification will see stale files. Also purge every zone that serves the content; Volume and Standard zones do not share cache.

Source URL: https://github.com/divinevideo/divine-blossom/blob/HEAD/docs/measurements/2026-08-07-takedown-drill.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Jt9UU4boRqYznFDRxNvNYA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bunny purge wildcard: use {hash}* not {hash}/* <span>— Vectle</span></a>

Bunny purge wildcard: use {hash}* not {hash}/* | Vectle