# Gcore CDN

> Configure Gcore CDN resources for content delivery including origin groups, caching rules, SSL certificates, HTTP headers, cache purge, logs, Grafana dashboards, and Terraform integration.

- [CDN](https://docs.gcore.com/cdn.md): Configure Gcore CDN resources for content delivery including origin groups, caching rules, SSL certificates, HTTP headers, cache purge, logs, Grafana dashboards, and Terraform integration.

## Getting Started

## Create a CDN resource
- [CDN resource overview](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/overview.md): Create CDN resources for entire site acceleration, static asset delivery (images, CSS, JavaScript, fonts), or video streaming (HLS, DASH, FLV) with integrated or manual DNS management and up to thirty resources per account.
- [Create a CDN resource](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource.md): Create a CDN resource by entering a domain name, choosing a DNS option (CNAME-based or Gcore Managed DNS delegation), optionally enabling WAAP for Layer 7 DDoS and web application protection, and configuring an origin or origin group.
- [Create a CDN resource for video streaming](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource-for-video-streaming.md): Create a CDN resource for video streaming with HLS, DASH, FLV, or MP4 formats, configuring geo-blocking, secure token authentication, custom domains, and origin shielding for global delivery without transcoding.

## Integrate CDN with CMS and other platforms
- [About Gcore CDN integration with CMS and other platforms](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms.md): Integrate Gcore CDN with CMS platforms and cloud storage by replacing application domain with custom CDN domain using plugins for WordPress, Drupal, Joomla, Magento, PrestaShop, AWS S3, Google Cloud Storage, Cloudflare, and other supported platforms.
- [Integrate CDN resource with AWS S3](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-aws-s3.md): Configure Gcore CDN resource with AWS S3 bucket as origin by creating S3 bucket, enabling Static Website Hosting, setting bucket policy, and using S3 Endpoint URL as CDN origin source with CNAME record.
- [Integrate CDN resource with B2evolution](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-b2evolution.md): Configure B2evolution CMS to serve static resources through Gcore CDN by replacing base URL variables with CNAME domain in configuration file, then verify resource URLs are rewritten to CDN CNAME in browser Network tab.
- [Integrate CDN resource with Cloudflare](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-clouldflare.md): Configure Gcore CDN integration with Cloudflare by disabling DNS proxying on CNAME records and setting Origin Pull Protocol to HTTP or adding Change SNI Hostname in Security settings to avoid 502 errors.
- [Integrate CDN resource with Concrete5](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-concrete5.md): Configure Gcore CDN resource integration with Concrete5 CMS by installing CDN extensions (CDN Manager, Content Delivery Network, or concrete5 CDN package) and entering the CNAME custom domain in extension settings to rewrite static file URLs.
- [Integrate CDN resource with Craft](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-craft.md): Configure Gcore CDN resource integration with Craft CMS by creating a new asset source with CDN CNAME, uploading static files, and replacing asset URLs to enable content delivery through the CDN endpoint.
- [Integrate CDN resource with Cs-cart](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-cs-cart.md): Install the Gcore CDN Universal Add-on plugin for Cs-cart, configure the CDN URL field with a CNAME record from Gcore Customer Portal, and enable the plugin to rewrite static file URLs through the CDN resource.
- [Integrate CDN resource with Django CMS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-django-cms.md): Configure Django CMS static and media file delivery through Gcore CDN by creating a CDN resource, updating urls.py and settings.py to point to CDN CNAME, and running collectstatic to serve static assets via CDN.
- [Integrate CDN resource with Drupal](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-drupal.md): Enable Gcore CDN integration with Drupal by installing the CDN Module, configuring Origin Pull mode with CNAME from Gcore Customer Portal, setting Far Future expiration, and enabling HTTPS for SSL support.
- [Integrate CDN resource with Google Cloud Storage](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-google-cloud-storage.md): Configure Gcore CDN resource with Google Cloud Storage bucket as origin, create CNAME record for custom domain, and optionally use Rewrite option to hide bucket name.
- [Integrate CDN resource with IPB](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ipb.md): Configure Gcore CDN CNAME integration with Invision Power Board by entering custom domain in System settings General configuration to rewrite image, CSS, and JavaScript URLs.
- [Integrate CDN resource with IPS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ips.md): Configure Gcore CDN CNAME integration with IPS Community by entering the custom domain in System Settings General Configuration CDN Settings and verifying URL rewriting in browser developer tools.
- [Integrate CDN resource with Joomla](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-joomla.md): Install the CDN for Joomla plugin from NoNumber.nl via Extensions Manager, configure the CNAME record from Gcore Customer Portal in plugin settings, and verify static file URLs are rewritten to the CDN CNAME domain.
- [Integrate CDN resource with Kirby](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-kirby.md): Configure CDN CNAME URLs for Kirby CMS static assets by manually updating CSS and JS file paths in header.php and using the Kirby GetImages plugin for image delivery, then verify rewritten URLs in browser Network tab.
- [Integrate CDN resource with Magento](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-magento.md): Configure Gcore CDN integration with Magento by enabling Merge JavaScript Files and Merge CSS Files in Developer settings, then set the CDN CNAME in Web > Unsecure or Secure > Base URL and Base Skin URL configuration sections.
- [Integrate CDN resource with Perch](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-perch.md): Configure Perch CMS to deliver static content through Gcore CDN by updating configuration files with CDN resource CNAME and bucket paths, then verify URL rewriting in browser developer tools.
- [Integrate CDN resource with PrestaShop](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-prestashop.md): Configure Gcore CDN integration with PrestaShop by enabling CCC (Combine, Compress and Cache) settings in Advanced Parameters/Performance and entering the CDN CNAME in the Media Server field to rewrite static asset URLs.
- [Integrate CDN resource with PyroCMS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-pyrocms.md): Configure Gcore CDN CNAME integration in PyroCMS admin panel via Settings > Integration to rewrite static asset URLs to custom domain.
- [Integrate CDN resource with SocialEngine](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-socialengine.md): Integrate CDN resource with SocialEngine by entering CNAME from Gcore Customer Portal in Settings/General Settings, ensuring CNAME record is properly configured, and verifying static file URLs are rewritten to the CDN CNAME domain.
- [Integrate CDN resource with Typo3](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-typo3.md): Configure Gcore CDN integration with Typo3 using the smile_cdn extension by installing the plugin, defining the CDN CNAME record, setting asset filters, and flushing frontend caches to rewrite static resource URLs.
- [Integrate CDN resource with vBulletin](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-vbulletin.md): Configure CDN resource integration with vBulletin by creating replacement variables in Styles > Replacement Variable Manager to rewrite static file URLs from origin to Gcore CDN CNAME domain.
- [Integrate CDN resource with Webasyst](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-webasyst.md): Configure Gcore CDN CNAME integration in Webasyst by entering the custom domain in Site Settings and verifying URL rewriting in browser Developer Tools.

## Wordpress
- [Integrate CDN resource with WordPress (Gcore plugin)](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-gcore-plugin.md): Install and configure the Gcore CDN WordPress plugin to enable CDN delivery by setting Enable CDN checkbox, Personal domain, file types (basic or advanced mode with custom extensions), folder paths, and exception URLs.
- [Integrate CDN resource with WordPress (Rocket plugin)](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-rocket-plugin.md): Configure Gcore CDN resource integration with WordPress using WP Rocket plugin by entering CNAME from Control Panel, updating Replace Site's Hostname field, and verifying static file URLs are rewritten to CDN CNAME domain.
- [Integrate CDN resource with WordPress (W3 Total Cache plugin)](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-w3-total-cache-plugin.md): Configure Gcore CDN integration with WordPress using W3 Total Cache plugin by enabling Generic Mirror CDN type and entering your CDN CNAME in the hostname replacement field.
- [Integrate CDN resource with WordPress (WP SuperCache plugin)](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-wp-supercache-plugin.md): Configure WP Super Cache plugin CDN integration by enabling CDN Support, entering Gcore CDN CNAME in Off-site URL field, and verifying static asset URLs are rewritten to the custom domain.
- [Integrate CDN resource with X-Cart](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-x-cart.md): Configure Gcore CDN resource integration with X-Cart 4.4.x by setting CNAME record in Customer Portal and modifying smarty.php, func.files.php, function.get_category_image_url.php, and banner_rotator.tpl files to rewrite static asset URLs to CDN CNAME domain.
- [Integrate CDN resource with XenForo](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-xenforo.md): Configure Gcore CDN resource integration with XenForo by editing config.php, updating Style General Settings with CDN CNAME domain, and verifying static file URLs are rewritten to the configured CNAME record.
- [Extend CDN functionality with FastEdge](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-fastedge.md): Integrate FastEdge CDN applications with a Gcore CDN resource to add custom request and response processing via Customer Portal or REST API.

## Configure an origin
- [Add CDN servers to the origin ACL whitelist](https://docs.gcore.com/cdn/getting-started/configure-an-origin/add-cdn-servers-to-the-origin-acl-whitelist.md): Configure origin ACL whitelist for CDN servers using HTTP headers, IP addresses, or subnets via API endpoints; HTTP header method recommended to avoid manual updates as CDN server IPs change every 30-60 minutes.
- [Сonfigure HTTP/2 on the origin](https://docs.gcore.com/cdn/getting-started/configure-an-origin/configure-http-2-on-the-origin.md): Enable HTTP/2 protocol on CDN origin servers by configuring Nginx 1.9.5+ with listen directive or Apache 2.4.17+ with mod_http2 module to support multiplexed content delivery over single TCP connections.
- [CDN timeouts](https://docs.gcore.com/cdn/getting-started/cdn-timeouts.md): Configure Gcore CDN Edge Network proxy timeouts including proxy_read_timeout (30s), proxy_connect_timeout (5s), proxy_send_timeout (30s), and client_header_timeout for origin server connections and client request handling.
- [About CDN resources interface: how it is arranged](https://docs.gcore.com/cdn/about-cdn-resources-interface-how-it-is-arranged.md): Create and manage CDN resources in the Gcore Customer Portal with filtering by status (Active, Suspended, Processing, Deleted), search by CNAME or resource ID, and per-resource operations including Settings, Statistics, Suspend resource, LIVE STREAMING preset, and Delete resource. Purge and Prefetch are accessible from the CDN navigation menu.
- [Add an origin group to a CDN resource](https://docs.gcore.com/cdn/add-an-origin-group.md): Create and attach origin groups to CDN resources with single or multiple origins, configuring round-robin load balancing between active origins and backup failover logic for 5xx errors.

## CDN resource options

## General
- [Specify an origin and the origin pull protocol](https://docs.gcore.com/cdn/cdn-resource-options/general/specify-an-origin-and-the-origin-pull-protocol.md): Configure CDN origin pull protocol (HTTP, HTTPS, or HTTP and HTTPS) and specify origin server IP address or domain for content delivery, controlling which protocol CDN servers use to fetch content from the origin and how client requests are routed based on protocol matching.
- [Use a private bucket as an origin](https://docs.gcore.com/cdn/cdn-resource-options/general/use-a-private-bucket-as-an-origin.md): Configure private S3-compatible buckets as CDN origins using per-origin AWS Signature V4 authentication and optional per-origin Host header overrides for Amazon or Gcore Object Storage.
- [Enable origin SSL validation](https://docs.gcore.com/cdn/cdn-resource-options/general/enable-origin-ssl-validation.md): Enable origin SSL validation for CDN resources by uploading X.509 certificates in PEM format via the Add Trusted CA Certificate API endpoint, then linking certificates to CDN resources using proxy_ssl_ca, proxy_ssl_data, and proxy_ssl_enabled parameters to verify origin server identity and prevent Man-in-the-Middle attacks.
- [Create and set a custom domain for the content delivery via CDN](https://docs.gcore.com/cdn/cdn-resource-options/general/create-and-set-a-custom-domain-for-the-content-delivery-via-cdn.md): Create custom domains and additional domains for CDN static content delivery by specifying domain names in the CDN resource configuration and adding CNAME records pointing to the account-specific gcdn.co endpoint.
- [Enable and configure origin shielding](https://docs.gcore.com/cdn/cdn-resource-options/general/enable-and-configure-origin-shielding.md): Enable Gcore CDN origin shielding to route edge requests through a shield that caches content and fetches from origin on cache miss, reducing origin load.
- [Suspend a CDN resource automatically or manually](https://docs.gcore.com/cdn/cdn-resource-options/general/suspend-a-cdn-resource-automatically-or-manually.md): Suspend CDN resources automatically after 90 days of inactivity or manually via Content availability toggle in resource settings; automatic suspension triggers email notifications to administrator and engineer roles 7 days before suspension.
- [Customize connection and read timeouts](https://docs.gcore.com/cdn/cdn-resource-options/general/customize-connection-and-read-timeouts.md): Configure custom connection timeout and read timeout for CDN resources to specify how long edge nodes wait when connecting to origin servers and receiving responses before returning 504 Gateway Timeout errors.

## Cache
- [Specify cache lifetime on a CDN resource or origin](https://docs.gcore.com/cdn/cdn-resource-options/cache/specify-cache-lifetime-on-a-cdn-resource-or-origin.md): Configure CDN cache lifetime with origin or CDN controlled settings, advanced caching rules, video TTL guidance, and cache header checks.
- [Set up a CDN resource to follow origin redirects](https://docs.gcore.com/cdn/cdn-resource-options/cache/set-up-a-cdn-resource-to-follow-origin-redirects.md): Enable CDN origin redirection to follow HTTP 3xx status codes (301, 302, 303, 307, 308) returned by the origin server, with automatic content retrieval and caching via Gcore Customer Portal or API using the enabled and codes properties.
- [Specify cache lifetime for user browsers](https://docs.gcore.com/cdn/cdn-resource-options/cache/specify-cache-lifetime-for-user-browsers.md): Configure browser cache lifetime using Origin controlled mode with Cache-Control headers or CDN controlled mode with custom max-age values in seconds, controlling Cache-Control, Expires, and X-Cached-Since response headers for HTTP status codes 200, 201, 204, 206, 301, 302, 303, 304, 307, 308.
- [Ignore the set cookie or query string parameters when caching content on CDN servers](https://docs.gcore.com/cdn/cdn-resource-options/cache/ignore-the-set-cookie-or-query-string-parameters-when-caching-content-on-cdn-servers.md): Configure CDN query string caching behavior using Ignore All, Ignore All Except, or Ignore Only modes to control cache key generation for URLs with query parameters.
- [Always online: provide the stale cache if the origin is unavailable](https://docs.gcore.com/cdn/cdn-resource-options/cache/always-online-provide-the-stale-cache-if-the-origin-is-unavailable.md): Configure Always Online to serve stale cached content when origin is unavailable due to network errors, timeouts, invalid headers, or HTTP 5xx/4xx errors, with X-Cache - Stale response header and automatic origin availability checks per request.
- [Сache Sharding: share cache between CDN servers](https://docs.gcore.com/cdn/cdn-resource-options/cache/cache-sharding-share-cache-between-cdn-servers.md): Enable Cache Sharding on CDN resources to share cache between servers in the same Point of Presence using consistent hashing algorithm, improving cache hit rates for content-heavy applications like e-commerce, video streaming, and VoD platforms.
- [Modify cache key](https://docs.gcore.com/cdn/cdn-resource-options/cache/modify-cache-key.md): Configure cache key variables (URI, protocol, normalized URI) in Gcore CDN resources via portal or API to control cache object identification and improve cache hit ratio.

## Access
- [Control access to the content with country, referrer, IP, and user agents policies](https://docs.gcore.com/cdn/cdn-resource-options/security/control-access-to-the-content-with-country-referrer-ip-and-user-agents-policies.md): Configure CDN resource access policies by country, referrer domain, and IP address ranges using allow or block rules in Resource settings via portal or API.
- [Set up a redirect from HTTP to HTTPS](https://docs.gcore.com/cdn/cdn-resource-options/security/set-up-a-redirect-from-http-to-https.md): Configure HTTP to HTTPS redirect on CDN resources via Gcore Customer Portal Access section or API, requiring an active SSL certificate in the General section first.

## Secure token
- [About secure token](https://docs.gcore.com/cdn/cdn-resource-options/security/use-a-secure-token/about-secure-token.md): Configure Gcore CDN Secure Token to protect content with time-based expiration and IP address restrictions, returning 410 Gone responses for expired tokens and unauthorized IP requests.
- [Configure and use secure token](https://docs.gcore.com/cdn/cdn-resource-options/security/use-a-secure-token/configure-and-use-secure-token.md): Configure secure token in Gcore CDN resources by enabling the option, setting a 6-32 character key, optionally binding to client IP, and generating MD5-hashed secure links with Unix timestamp expiration using PHP, Python, or OpenSSL scripts; validate token hash, expiration timestamp, and file or directory path on each request.
- [Specify HTTP methods allowed for content requests from the CDN](https://docs.gcore.com/cdn/cdn-resource-options/security/specify-http-methods-allowed-for-content-requests-from-the-cdn.md): Configure allowed HTTP methods (GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS) for CDN resources via the Enable HTTP methods toggle to block unauthorized requests and return 405 Method Not Allowed responses.
- [Set the hostname passed in SNI requests to the origin](https://docs.gcore.com/cdn/cdn-resource-options/security/set-the-hostname-passed-in-sni-requests-to-the-origin-server.md): Configure SNI hostname in CDN HTTPS origin requests using Dynamic mode matching Host Header or Custom mode with a specified hostname value.
- [Specify TLS versions allowed for content requests from the CDN](https://docs.gcore.com/cdn/cdn-resource-options/security/choose-tls-versions.md): Configure allowed TLS protocol versions (SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3) for CDN content requests via the Gcore Customer Portal to block unspecified versions.

## Security
- [Protect CDN resources with Gcore WAAP](https://docs.gcore.com/cdn/cdn-resource-options/cdn-security/protect-cdn-resources-with-basic-waf.md): Enable WAAP (Web Application and API Protection) for CDN resources via the Customer Portal Security section to activate Layer 7 DDoS protection, web app security, and API protection; create CDN rules with WAAP exceptions to prevent blocking legitimate content by matching URLs or regex patterns.

## Compression
- [Configure Gzip and Brotli compression](https://docs.gcore.com/cdn/cdn-resource-options/compression/configure-gzip-and-brotli-compression.md): Enable Gzip and Brotli edge compression in Gcore CDN to compress content at edge nodes before serving to browsers, supporting MIME types including text/html, application/javascript, application/json, image/svg+xml, and application/wasm with configurable compression methods based on Accept-Encoding headers.
- [Configure fetch compression](https://docs.gcore.com/cdn/cdn-resource-options/compression/configure-fetch-compression.md): Enable Fetch compressed in CDN resource Content settings to pull already-compressed content from origin servers supporting GZip compression, reducing bandwidth and delivery time between origin and CDN edge servers.
- [Configuring HTTP status codes for CDN-hosted content](https://docs.gcore.com/cdn/cdn-resource-options/specify-custom-http-status-code-for-the-content-delivered-by-the-cdn.md): Configure custom HTTP status codes for Gcore CDN resources globally via Resource settings or selectively via Rules, with optional redirect URLs, status text, and time-based scheduling by timezone.
- [Optimize large file delivery](https://docs.gcore.com/cdn/cdn-resource-options/optimize-large-file-delivery.md): Enable Large File Delivery Optimization in Gcore CDN to serve files larger than 10 MB using HTTP Range requests with 10 MB chunks, requiring origin support for Range Requests, consistent Content-Length and Etag headers, and incompatibility with Fetch Compressed, Gzip Compression, and Brotli Compression options.
- [Rewrite: redirect requests from the CDN to the origin](https://docs.gcore.com/cdn/cdn-resource-options/rewrite-redirect-requests-from-the-cdn-to-the-origin.md): Configure CDN Rewrite option with nginx-compatible regular expressions to redirect request paths from CDN to origin, using space-separated directives with capture groups ($1, $2) and optional flags like break, last, redirect, permanent.
- [WebSockets: allow permanent connections with the origin](https://docs.gcore.com/cdn/cdn-resource-options/websockets-allow-permanent-connections-with-the-origin.md): Enable or disable WebSocket protocol support on CDN resources to allow persistent bidirectional TCP connections between clients and origin servers for real-time data exchange.

## HTTP headers
- [Specify HTTP headers that CDN adds to requests to the origin](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/specify-http-headers-that-cdn-adds-to-requests-to-the-origin.md): Configure HTTP request headers that Gcore CDN adds to origin requests via the Request Headers option, specifying header names and values with supported characters (letters, numbers, dashes, underscores, slashes, colons, equals, dots, spaces).
- [Add the Access-Control-Allow-Origin header to the browser response](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/add-the-access-control-allow-origin-header-to-the-browser-response.md): Configure Access-Control-Allow-Origin CORS headers in Gcore CDN resources via resource settings, rule creation, or origin server to allow cross-origin requests from specific domains or all origins using wildcard or domain whitelist options.
- [Add or hide response headers](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/add-or-hide-response-headers.md): Configure custom HTTP response headers in Gcore CDN via the "Response headers (add)" option to add up to 50 headers with custom names and values to CDN server responses, supporting multiple values per header separated by commas or line breaks and filtering by HTTP status codes.
- [Configure and check the host header](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/configure-and-check-the-host-header.md): Configure the Host header in Gcore CDN resources using Custom Host header or Forward Host header options in HTTP headers settings to specify origin domain/IP address, and verify header values with curl or diagnostic tools to prevent 4xx/5xx errors.
- [Use the X-Forwarded-Proto header to identify the protocol used for CDN servers requests](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/use-the-x-forwarded-proto-header-to-identify-the-protocol-used-for-cdn-servers-requests.md): Configure X-Forwarded-Proto header in CDN to identify client protocol (HTTP or HTTPS) for implementing HTTP-to-HTTPS redirects and protocol-based content delivery.
- [Network limits: set the content delivery speed to end users](https://docs.gcore.com/cdn/cdn-resource-options/network-limits-set-the-content-delivery-speed-to-end-users.md): Configure CDN Download Speed Limit in Static or Dynamic mode to control content delivery speed per connection in KB/s, with parameters for Connection Speed, Limit After, speed query argument, and buffer argument.

## Image optimization (paid)
- [About image stack](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/about-image-stack.md): Configure Image Stack to optimize JPG and PNG images on the fly using quality adjustment, WebP/AVIF compression, resize, and crop operations; optimized versions cache on CDN while original images remain unchanged and X-Img-Operations headers track transformations.
- [Enable image stack](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/enable-image-stack.md): Enable Image Stack option for CDN resources via Gcore Support, then configure image quality (High/Medium/Low/Custom 0-100%), WebP and AVIF compression, and resize/crop parameters through CDN resource Rules with the image optimization template.

## Image stack tools
- [Сonfigure image compression to WebP and AVIF](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/configure-image-compression-to-webp-and-avif.md): Enable WebP and AVIF image compression in Gcore CDN to automatically convert JPG and PNG images to modern optimized formats via Customer Portal Image optimization rules or query string parameters.
- [Change image quality](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/change-image-quality.md): Configure image quality reduction in Gcore CDN Image Stack via portal settings or query string parameters (quality values - High, Medium, Low, or custom percentage) applied alongside format conversion (WebP, AVIF) or other transformations (Crop, Resize).
- [Crop images](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/crop-images.md): Configure image cropping in Gcore CDN using query string parameters to specify aspect ratio, dimensions, and crop location before image delivery via the Image Stack paid feature.
- [Reduce image size](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/reduce-image-size.md): Configure Resize query parameters (width, height) in image URLs to reduce JPG and PNG dimensions on Gcore CDN with automatic aspect ratio preservation or cropping via Image Stack feature.
- [Possible image stack errors](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/possible-image-stack-errors.md): Troubleshoot Image Stack errors by examining HTTP status codes, response headers (X-Img-Server, X-IMG-Saved-Bytes, X-IMG-Processing-Time, X-GCDN-Origin-Size), and request methods using browser developer tools to identify broken images, missing processing, or incorrect GET requests.
- [Query String Forwarding: forward parameters to sub-requests](https://docs.gcore.com/cdn/cdn-resource-options/query-string-forwarding.md): Configure Query String Forwarding in Gcore CDN to copy query string parameters from parent manifest requests to nested HLS and MPEG-DASH file requests, specifying forward_from_file_types, forward_to_file_types, and forward_only_keys via portal or API.
- [Determine in which regions the content will be delivered with Geobalancer for paid tariffs](https://docs.gcore.com/cdn/cdn-resource-options/determine-in-which-regions-the-content-will-be-delivered-with-geo-balancer-for-paid-tariffs.md): Configure Geobalancer to restrict content delivery to specific regions (North America, Latin America, Asia, Middle East, Australia, Africa, Europe) and set default location handler fallback regions (Asia, Near East, Middle America, Europe) for paid CDN tariffs to optimize Cache Hit Ratio.

## Rules for particular files
- [Create a rule manually or from a template to configure settings for particular files](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/create-a-rule-manually-or-from-a-template-to-configure-settings-for-particular-files.md): Create CDN rules to override resource-level settings for specific file paths using URI patterns or regex, configuring cache lifetime, origin protocol, and other CDN options per rule with a maximum of five custom rules per resource.
- [Create a CDN resource rule template manually or use a system one](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/create-a-cdn-resource-rule-template-manually-or-use-a-system-one.md): Create custom CDN resource rule templates with file paths, origin pull protocol (HTTP, HTTPS, Inherit from resource), and additional options, or apply system templates for video streaming (.ts, .m3u8), Let's Encrypt HTTP-01 challenge validation, and static content caching.
- [Avoid indexing of your CDN resource by web crawlers](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/set-robots-txt-to-avoid-adding-to-index-by-web-crawlers.md): Configure Status code rules on CDN custom domains to return HTTP 403 Forbidden responses and prevent web crawlers from indexing duplicate content across CDN and origin domains.
- [Clear CDN resource cache by URL, pattern, or all and check purge history](https://docs.gcore.com/cdn/clear-cdn-resource-cache-by-url-pattern-or-all.md): Clear CDN resource cache by URL, pattern, or all using Gcore CDN Purge API or Customer Portal, with purge history tracking and rate limits of two requests per resource per minute.

## Grafana
- [View CDN statistics in Grafana](https://docs.gcore.com/cdn/grafana/view-cdn-statistics-in-grafana.md): Display CDN statistics in Grafana using the cdn-stats plugin to visualize Total Traffic, Byte Cache Hit Ratio, Edges Traffic, Shield Traffic, Origin Traffic, Total Requests, HTTP response codes (2xx, 3xx, 4xx, 5xx), Bandwidth, Cache Hit Ratio, and Shield Traffic Ratio, grouped by Clients, Resource, Region, Country, Data Center, or Vhost parameters.
- [How the CDN service and its additional options are billed](https://docs.gcore.com/cdn/how-the-cdn-service-and-its-additional-options-are-billed.md): Configure CDN billing plans with monthly traffic limits, traffic overage charges, and request overage fees; traffic renews monthly and includes origin-to-CDN and CDN-to-end-user traffic.

## IP configuration options
- [Bring Your Own IP](https://docs.gcore.com/cdn/ip-configuration-options/byoip.md): Enable Bring Your Own IP (BYOIP) to announce custom IP subnets from Gcore's ASN or bring your own ASN for IP address management and network customization.
- [Dedicated IP](https://docs.gcore.com/cdn/ip-configuration-options/dedicated-ip.md): Enable Dedicated IP addresses or subnets to isolate sensitive content from shared IP networks and reduce reputation risk from other users' traffic.
- [Load content to the CDN before users request it](https://docs.gcore.com/cdn/load-the-content-to-cdn-before-users-request-it.md): Enable CDN Prefetch to preload content into cache before user requests using file paths, supporting files 200 MB to 5 GB with maximum 100 paths per request and 1 request per minute limit.

## Logs
- [Logs uploader](https://docs.gcore.com/cdn/logs/logs-uploader.md): Configure CDN Logs uploader to export request and cache behavior logs to Object Storage, S3-compatible, FTP, SFTP, or HTTP(S) destinations via Configurations, Policies, and Targets tabs with field selection, delivery frequency, and target authentication management.
- [Log viewer: view and download CDN resource logs](https://docs.gcore.com/cdn/logs/log-viewer-view-and-download-cdn-resource-logs.md): View and download CDN resource logs using Log viewer with filters for time interval, client IP, HTTP method, status code, data center, and cache status; export up to 10,000 log entries per 24-hour period.

## SSL certificates
- [Add an SSL certificate to deliver content over HTTPS](https://docs.gcore.com/cdn/ssl-certificates/add-an-ssl-certificate-to-deliver-content-over-https.md): Attach SSL certificates to CDN resources for HTTPS delivery using custom domains, supporting both third-party certificates and free Let's Encrypt certificates via Gcore Customer Portal.
- [Configure your own SSL certificate](https://docs.gcore.com/cdn/ssl-certificates/configure-your-own-ssl-certificate.md): Upload custom SSL certificates in PEM format with certificate chain (personal certificate, intermediate CA, root CA) and private key to Gcore CDN, then attach to CDN resources for custom domains and wildcard subdomains.
- [Configure Let's Encrypt certificate](https://docs.gcore.com/cdn/ssl-certificates/configure-lets-encrypt-certificate.md): Enable HTTPS with free Let's Encrypt certificates on CDN resources using HTTP-01 or DNS-01 challenge validation, with optional Gcore Managed DNS delegation to ns1.gcorelabs.net and ns2.gcdn.services for domain ownership verification.

## Terraform
- [Manage CDN resources with Terraform v0](https://docs.gcore.com/cdn/terraform/manage-cdn-via-terraform.md): Create and manage Gcore CDN resources using Terraform provider v0. Covers origin groups with host and S3 origins, CDN resources with delivery options, SSL certificates (automated and manual), CA certificates for origin verification, CDN rules, rule templates, presets, account configuration, origin shielding (premium), and CDN logs uploader (premium). Uses gcore_cdn_origingroup, gcore_cdn_resource, gcore_cdn_sslcert, gcore_cdn_cacert, gcore_cdn_rule, gcore_cdn_rule_template, gcore_cdn_applied_preset, gcore_cdn_client_config, gcore_cdn_originshielding, gcore_cdn_logs_uploader_policy, gcore_cdn_logs_uploader_target, gcore_cdn_logs_uploader_config resources.
- [Manage CDN resources with Terraform v2](https://docs.gcore.com/cdn/terraform/manage-cdn-via-terraform-v2.md): Create and manage Gcore CDN resources using Terraform provider v2. Covers origin groups with host and S3 sources using list syntax, CDN resources with map-style options, SSL certificates with write-only fields, CA certificates, CDN resource rules, and rule templates. Uses gcore_cdn_origin_group, gcore_cdn_resource, gcore_cdn_certificate, gcore_cdn_trusted_ca_certificate, gcore_cdn_resource_rule, gcore_cdn_rule_template resources. Key v2 changes from v0 include map-syntax options, write-only S3 credentials, and renamed certificate fields.

## Troubleshooting
- [Common Setup Issues](https://docs.gcore.com/cdn/troubleshooting/common-setup-issues.md): Resolve CDN setup issues including 503 service unavailable errors from unreachable origins, ERR_TOO_MANY_REDIRECTS from HTTP-to-HTTPS redirect loops, incorrect MIME type headers causing file downloads, and Let's Encrypt SSL certificate validation failures due to DNS propagation delays.
- [Resolve errors by status code for GCore CDN](https://docs.gcore.com/cdn/troubleshooting/gcore-error-status-codes.md): Resolve HTTP 403 and 404 status code errors in Gcore CDN by checking Log viewer delivery status, enabling disabled CDN resources, and adjusting security policies for Referrer, Country, IP, and User-Agent restrictions.
- [Traceparent header for troubleshooting](https://docs.gcore.com/cdn/troubleshooting/traceparent-header-for-troubleshooting.md): Enable W3C Trace Context traceparent header support in Gcore CDN to track requests across services using trace-id, parent-id, trace-flags, and tracestate fields; forward traceparent headers to origin while modifying only parent-id, and access traceparent values in response headers and Raw Logs for request troubleshooting.
- [Content is unavailable after a CDN resource creation: how to solve the issue](https://docs.gcore.com/cdn/troubleshooting/content-is-unavailable-after-a-cdn-resource-creation-how-to-solve-the-issue.md): Troubleshoot CDN resource content unavailability by verifying origin HTTP 200 response codes, checking CNAME record configuration in DNS settings, and validating Host Header options in CDN resource settings.
- [Cache hit ratio is low: How to solve the issue](https://docs.gcore.com/cdn/troubleshooting/cache-percentage-is-low-how-to-solve-the-issue.md): Monitor cache hit ratio in Gcore CDN Statistics to identify low cache delivery efficiency; check Cache-Control and Cache response headers on edge servers using X-id header tracking to diagnose origin requests and content delivery delays.
- [Content delivery speed is low: how to solve the issue](https://docs.gcore.com/cdn/troubleshooting/content-delivery-speed-is-low-how-to-solve-the-issue.md): Diagnose and resolve low CDN content delivery speed by comparing origin and CDN performance using DevTools, wget, or online speed tests, then optimize CDN-resource settings including cache hit ratio, large file delivery, and gzip/brotli compression.
- [An SSL certificate isn't working: how to solve the issue](https://docs.gcore.com/cdn/troubleshooting/an-ssl-certificate-isn-t-working-how-to-solve-to-issue.md): Troubleshoot CDN SSL certificate attachment errors, Let's Encrypt issuance failures, and browser TLS handshake errors including SSL_ERROR_INTERNAL_ERROR_ALERT.
- [3xx error: how to solve CDN issues with redirect](https://docs.gcore.com/cdn/troubleshooting/3xx-error-how-to-solve-cdn-issues-with-redirect.md): Resolve CDN 3xx redirect errors by configuring origin pull protocol (HTTP or HTTPS) to match origin redirect settings, updating Host Header to match the origin domain, and setting the correct Origin source for redirected domains.
- [4xx error: how to solve CDN issues with the limited access and content non-existence](https://docs.gcore.com/cdn/troubleshooting/4xx-error-how-to-solve-cdn-issues-with-the-limited-access-and-content-non-existence.md): Diagnose and resolve 4xx errors in Gcore CDN by verifying origin content availability, allowlisting CDN edge IPs, configuring Origin Pull Protocol, and validating Host Header settings; use Reports, Log viewer, and Raw logs to track error sources.
- [5xx error: how to solve server issues](https://docs.gcore.com/cdn/troubleshooting/5xx-error-how-to-solve-server-issues.md): Diagnose and resolve HTTP 5xx errors on CDN edge servers and origin servers by checking Gcore Status Page for incidents, verifying origin availability and response times, whitelisting CDN edge server IPs in origin ACL, and configuring correct origin pull protocol and Host Header settings in CDN resource options.

## Video CDN
- [Video CDN Overview](https://docs.gcore.com/cdn/video-cdn/video-cdn-overview.md): Configure Video CDN to deliver HLS, DASH, HTTP-FLV, and MP4 video streams through Gcore CDN edge locations worldwide; requires Support approval with Client ID, domain, content type, and licensing verification for live and VOD workflows.
- [Common Media Client Data (CMCD)](https://docs.gcore.com/cdn/video-cdn/cmcd.md): Use Common Media Client Data (CMCD) with Gcore Video CDN to collect player-side playback and delivery metrics in query strings or request headers, improve CDN observability, and help Gcore Support investigate video playback issues.
- [HLS and LL-HLS via CDN](https://docs.gcore.com/cdn/video-cdn/hls.md): Deploy HLS and LL-HLS video streams via Gcore CDN using HTTP-based adaptive streaming with master playlists, media playlists, fMP4 CMAF segments, and partial segments; configure cache rules, query parameter whitelisting, and LIVE STREAMING preset for low-latency delivery.
- [Improve video delivery speed for low-traffic accounts](https://docs.gcore.com/cdn/video-cdn/improve-video-delivery-speed.md): Troubleshoot slow video delivery by checking CDN cache hits, origin 404s, live player requests, TTLs, Origin Shielding, and prefetch.
- [DASH and LL-DASH via CDN](https://docs.gcore.com/cdn/video-cdn/dash.md): Deploy MPEG-DASH and LL-DASH (Low-Latency DASH) streams via Gcore CDN using .mpd manifests and CMAF segments with Chunked-Proxy technology to achieve 2-4 second glass-to-glass latency for live video delivery.
- [Multi-codec VOD delivery over CDN](https://docs.gcore.com/cdn/video-cdn/multi-codec-vod-delivery.md): Deliver multi-codec VOD streams including HEVC, AV1, VP9, and H.264 renditions through Gcore CDN to reduce bandwidth consumption by 25-60% depending on codec choice and device compatibility.
- [Origin shielding for video delivery](https://docs.gcore.com/cdn/video-cdn/origin-shielding-for-video.md): Enable origin shielding for video CDN delivery to add a precache shield server between origin and edge locations, reducing concurrent origin requests, origin egress costs, and improving reliability during live events and VOD cache misses.
- [Secure Token for Video CDN](https://docs.gcore.com/cdn/video-cdn/secure-token.md): Enable Secure Token and Query String Forwarding in Video CDN to protect HLS and MPEG-DASH streams with temporary access tokens, forwarding token parameters from master manifests to nested manifests, segments, and subtitles via directory-path token rules.
- [Auto-refresh CDN secure tokens](https://docs.gcore.com/cdn/video-cdn/secure-token-auto-refresh.md): Configure CDN Secure Token auto-refresh with 60-second expiration and query string parameters or path-based tokens to prevent link sharing during live streams and pay-per-view events, supporting plain or IP-bound token validation modes.
- [Troubleshoot video delivery](https://docs.gcore.com/cdn/video-cdn/troubleshoot-video-delivery.md): Diagnose and fix common video delivery problems on CDN that end viewers experience
- [HTTP-FLV Live and VOD Delivery](https://docs.gcore.com/cdn/video-cdn/flv-streaming.md): Deploy HTTP-FLV Live streaming with ultra-low latency (1-3 seconds) and high concurrency (100K+ simultaneous viewers) using Gcore CDN's dedicated FLV Live profile; configure origin to deliver FLV container with proper headers, monotonic PTS/DTS timestamps, H.264/H.265/AAC codecs, and HTTP 200 responses cached via sliding window RAM buffer.
- [View statistics of CDN resources](https://docs.gcore.com/cdn/view-statistics-of-a-cdn-resource.md): View CDN resource statistics including traffic, bandwidth, response codes, cache hit ratio, requests, regional traffic distribution, image optimization WebP conversions, request time, and upstream response times via the Statistics tab, or enable Advanced Analytics for filtered reports on requests, traffic, and unique visitors by country, directory, browser, device, and operating system.