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/Kirby

Integrate CDN resource with Kirby

Before you take any steps please back up your files and database. The plugin works only with default CMS pattern. If you manually changed CMS patterns, the plugin might not help you.

There is currently no plugin available for automatic CDN integration with Kirby. You need to change manually the path for your CSS and JS files in the header.php but there is the Kirby GetImages plugin for your images. For more details visit GitHub.

We highly recommend you to check the HTML code of your web page to ensure that URLs have been rewritten properly from your original ones to CNAME from the Gcore Customer Portal.

To do that press F12 or open Developers Tools in your browser, choose the Network tab and refresh the page. All static files should have your CNAME in URLs.

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page

Edit on GitHub