- Static files are cached by all Regions for 31 days by default. If you need to configure this duration, you can set a
Cache-Control header in your
- Dynamic responses (from Lambdas) are not cached unless they contain a
Cache-Control header with specific directives (e.g.
- Read more about this in the caching documentation.
- Your lambdas have total control on how the CDN caches your responses using the
- The transition is painless. All you have to do is point your NS records to our DNS infrastructure.
- Read more about DNS records in the DNS documentation.
- You can create a new deployment to invalidate the cache for your aliased deployment.
- Content will remain cached for staging URLs until it expires.
now dev allows you to run your applications locally just like it does in production, but make sure to install your project's dependencies first.
- The very first request is served synchronously.
- Subsequent requests are served from cache, and if stale, revalidated asynchronously in the background.
- Read more in the
s-maxage is the number of seconds a response is considered "fresh" by the CDN.
- After this period ends, the CDN will continue to serve the response from the edge but it's now considered "stale" so it will be requested again to your lambda in the background to get a "fresh" one.
- We strip the
stale-while-revalidate directive from your
Cache-Control so browsers don't get it.
- This allows you to always deliver the latest content to your visitors right after creating a new deployment (as opposed to waiting for browser cache to expire).
- Users who visit your deployments will automatically use the CDN Region that is geographically closest to them.
- On the Free plan there is no charge for bandwidth, but you are capped at 100GB per month.
- See our pricing page for more details.
- In the event of a DDoS we have measures in place to detect and mitigate bad actors.
- We don't currently have an image optimization service in place, if you'd like to see this feature then please let us know.
Origin Control: Off along with other custom caching rules in CloudFlare, in a
now.json file, set
s-maxage to 0 on your routes to disable any caching from ZEIT CDN.
- When a new deployment is made, you will have to find a way to purge the CloudFlare cache.