The Gcore Customer Portal is being updated. Screenshots may not show the current version.

Billing CDN resources overview

Specify an origin Private origin Enable SSL Validation Create a custom domain (CNAME)SSL certificates Enable shielding (paid)Suspend a CDN resource Connection and read timeouts

Configure CDN caching Set a redirect from an origin Configure browser caching Ignore Set Cookie or Query string Use stale cache if origin is unavailable Cache Sharding Modify cache key

Manage access policies Redirect from HTTP to HTTPS

Overview Configure and use

Specify HTTP methods Set SNI hostname

Gcore WAAP (Beta)

GZip, Brotli Fetch

Status code Large files delivery Rewrite WebSockets

Add request headers Activate CORS Configure response headers Manage the Host header Identify a user's request protocol

Image stack overview Enable Image stack

Convert to WebP or AVIF Change quality Crop Resize

Troubleshooting

Streaming via CDN (for paid tariffs)Geobalancer (for paid tariffs)

Create a rule Create a template for rules Avoid indexing

SSL overview Own SSL certificate Let's Encrypt certificate

Export CDN logs Log Viewer (free)

Grafana reports

Install and integrate with CDN Create and manage CDN resources Copy CDN resources Create a CDN rule Add an SSL certificate Set up version control and perform rollback

Error status codes Traceparent Content unavailability Low cache hit ratio Low content delivery speed Attaching or issuing an SSL certificate 3xx codes 4xx codes 5xx codes

Home/CDN/CDN resource options/Cache/Use stale cache if origin is unavailable

Always online: provide the stale cache if the origin is unavailable

The option allows serving stale cached content in case of the following errors: error (network or connectivity issues), timeout, invalid_header, updating (cache updating),http_500, http_502, http_503, http_504, http_403, http_404, http_429.

HTTP response for the stale content will contain the header X-Cache: Stale. CDN will check origin availability with each user’s request. As soon as the origin becomes available, fresh files will be cached and served. If the origin is unavailable for a long time, CDN will send Stale content until origin becomes available.

Please, note that when the site is unavailable, the CDN cache may have not enough content for a correct page display. Situations, when a user will not be able to see some images, style sheets, or other static content, are possible.

To manage this option go to your Resource Advanced Settings, find the Cache section and click Always online. You can enable the toggle and choose error codes for which a CDN serves stale content.

Always Online toggle enabled

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page

Edit on GitHub