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

Raw logs Logs uploader (near real-time)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/Getting Started/Integrate CDN with CMS and other platforms/ClouldFlare

Integrate CDN resource with ClouldFlare

CNAME record setup

If you use the CloudFlare DNS service, the CloudFlare servers function as proxy for all DNS records. The CloudFlare's DDoS protection and CDN services are based on that.

If you want to use Gcore as your CDN provider, disable the proxying in the CloudFlare DNS settings by clicking the cloud icon during the CNAME record creation.

CNAME record setup

Origin Pull Protocol setup

Due to the differences in our and CloudFlare's infrastructures, if you set HTTPS as your "Origin Pull Protocol", you will likely start getting 502 errors.

To avoid it, add the Change SNI Hostname option in the "Security" section or change "Origin Pull Protocol" to HTTP.

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page

Edit on GitHub