Home ci 31. edge-network: Edge Network Frequently Asked Questions (FAQ)

31. edge-network: Edge Network Frequently Asked Questions (FAQ)

Last updated on Aug 05, 2025

The Epycbyte Edge Network provides a robust solution for content delivery and edge computing. Below are answers to frequently asked questions related to the Epycbyte Edge Network.

What are the Epycbyte Edge Network defaults? Static files are cached by all regions for up to 31 days. You can override this duration by setting a Cache-Control header in the headers property in a epycbyte.json file. Dynamic responses (from Serverless Functions) are not cached unless they contain a Cache-Control header with specific directives (e.g., s-maxage).

How can I control the accepted cache headers (and values)? You can control how the Epycbyte Edge Network caches your responses by setting a Cache-Control header. This allows you to specify caching behavior for different resources.

What if I am using a CDN like Akamai, Fastly, Cloudflare? The transition is painless. All you have to do is configure DNS records to our DNS infrastructure.

How do I purge the Epycbyte Edge Network? You can create a new deployment to invalidate the cache for your Preview and Production Deployments. Content will remain cached for preview URLs until it expires.

What are the limits of the Epycbyte Edge Network? You can read more about our caching limits in the caching documentation.

Can I run the Epycbyte Edge Network logic on my local development machine? Using the epycbyte dev command through Epycbyte CLI will allow you to run your applications with additional Epycbyte Edge Network logic. Using epycbyte dev is not necessary with Next.js applications — the Epycbyte Edge Network logic is already built-in with the next dev command.

How exactly does stale-while-revalidate work for the first and subsequent requests? The first request is served synchronously. Subsequent requests are served from the cache and revalidated asynchronously if the cache is "stale." You can read more about this in the caching documentation.

What is the relation between the s-maxage header and stale-while-revalidate? The s-maxage header specifies a maximum age for cached responses, while stale-while-revalidate allows for asynchronous validation of the cache. These settings work together to optimize performance and consistency.

Is my browser aware of stale-while-revalidate? Browsers are not directly aware of stale-while-revalidate; this is a server-side setting that determines how long a response is considered valid before being revalidated.

What locations does the Epycbyte Edge Network cover? The Epycbyte Edge Network has a global network of servers, ensuring fast and reliable content delivery worldwide.

Can I redirect users to a specific region using the Epycbyte Edge Network? Yes, you can configure your application to route traffic through specific regions based on your user's location or other criteria.

Will I get charged for using the Epycbyte Edge Network? The Epycbyte Edge Network is included with your hosting plan. However, data transfer costs and overage fees may apply depending on your usage.

Is there an image optimization feature in the Epycbyte Edge Network? Yes, the Epycbyte Edge Network supports image optimization to reduce file sizes while maintaining quality. This can be configured through your epycbyte.json settings.

How do I use Cloudflare over the Epycbyte Edge Network? To integrate Cloudflare with the Epycbyte Edge Network, you will need to set up custom caching rules in Cloudflare. Additionally, you can disable caching from the Epycbyte Edge Network by setting s-maxage to 0 in your epycbyte.json file.

Last updated on July 22, 2024