Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+17 more

    Repair HTTP Cache Vary Key Bugs

    1

    Repair HTTP cache key bugs around Vary that serve compressed, localized, authenticated, or tenant-specific responses to the wrong request variant.

    $8.99

    30-day refund guarantee

    Secure checkout via Stripe

    0 installsSecurity scanned

    See it in action

    You say

    Repair our Node response cache: the store path includes Accept-Encoding after reading Vary, but lookup uses only URL, so identity clients sometimes receive gzip bytes. Build a fake origin and deterministic tests. Preserve TTL, eviction, revalidation, authorization, and response headers.

    Your agent does

    Variant-index defect found. The cache stores representations under a Vary-aware key but performs initial lookup through a URL-only alias that can point at the last stored encoding. The repair introduces one canonical variant index, normalizes only declared Vary headers, keeps TTL/eviction/revalidation policy unchanged, and verifies gzip, identity, locale, authorization, and 304 paths with a fake origin.

    What you get

    Prevent cross-tenant content leakage in shared cache layers.Align lookup and store paths to fix incorrect variant serving.Normalize Accept-Encoding and Locale headers for consistent cache keys.Ensure 304 revalidations target the correct representation index.

    About this skill

    The problem

    HTTP caches often serve incorrect variants when lookup and store keys disagree or when the Vary header is processed inconsistently. This leads to leaking authenticated content across sessions, serving compressed bytes to legacy clients, or 304 revalidations updating the wrong representation.

    What it does

    • Identifies discrepancies between cache lookup and storage paths in repository code.
    • Normalizes request-header selection for Accept-Encoding, Locale, and Authorization.
    • Aligns variant indexing to ensure the cache reconciles Vary headers learned after the origin response.
    • Repairs repository-level cache-key construction and tenant boundaries.
    • Generates deterministic local test fixtures to verify cache hits and misses across headers.

    Frameworks & tools

    Works with repository-level code for CDNs, application-level cache adapters, and proxy configurations. Requires access to Read, Edit, and Bash tools.

    Why this beats prompting it yourself

    Generic prompts often suggest simple TTL changes or cache clearing which mask the underlying logic error. This skill enforces a strict resource register and failure timeline analysis to fix the architectural disagreement between how keys are generated and how variants are stored.

    Use cases

    • Fixing localized content leaks where one user sees another's language or tenant data.
    • Repairing broken 304 Not Modified flows that refresh the wrong cached representation.
    • Ensuring identity-encoded clients never receive Gzip or Brotli payloads.
    • Standardizing cache key normalization across multi-layer CDN and app architectures.

    Known limitations

    Does not modify TTL, eviction policies, or origin response headers. Cannot access production environments, live secrets, or deployed state; it is limited to repository-level repairs.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • One-time purchase, yours forever

    Listedtoday

    Frequently Asked Questions