Dev
Generador de prompts de configuración de CDN
Used by developers, writers, and creators worldwide.
A CDN config prompt generator builds a focused, fill-in request you can hand to an AI assistant so it configures a content delivery network with caching that actually helps rather than caching the wrong things. Pick the provider — CloudFront, Cloudflare, Fastly, or a generic edge — and the content type, and it produces a prompt that asks for the origin and default behaviour, Cache-Control and TTLs suited to that content, a deliberate cache key, compression and modern protocols, forced HTTPS with security headers, and a cache invalidation strategy for deploys. Frontend engineers use it to speed up a site correctly and avoid the trap of caching personalised API responses. It runs in your browser and generates instantly. Pick the provider and content type, then paste the prompt into your assistant. The cache-key and invalidation guidance is what keeps a CDN from serving stale or wrong content after a release.
Read the complete guide — 5 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick your CDN provider.
- Choose the content type you are serving.
- Click Generate to build the prompt.
- Paste it into your AI assistant and adapt the origin details.
Use Cases
- •Getting a correct CDN configuration from an AI assistant
- •Choosing Cache-Control and TTLs for a content type
- •Defining a cache key that avoids serving wrong content
- •Setting up cache invalidation for deploys
- •Standardising CDN setup across providers
Tips
- →Cache hashed static assets aggressively, HTML briefly.
- →Be deliberate about which cookies and query strings enter the cache key.
- →Always force HTTPS and add HSTS at the edge.
- →Have an invalidation plan before you turn caching up.
FAQ
why is the cache key so important
The cache key decides what counts as the same response. Include the wrong cookie or header and you cache a personalised page for everyone; ignore a query string that changes content and you serve the wrong variant. The prompt makes the cache key an explicit decision.
how should TTLs differ by content
Hashed static assets can cache for a year because their URL changes when they change, an SPA HTML shell should cache briefly so deploys appear fast, and API responses often should not cache at all unless they are public and stable. The prompt tailors TTLs to the content.
why ask about invalidation
Caching is only safe if you can purge it. Without an invalidation plan, a deploy leaves users on old assets until the TTL expires. The prompt requires an explanation of how to invalidate so releases take effect promptly.
You might also like
Popular tools from other categories that share themes with this one.