Kontenum
English
English Bahasa Indonesia
Main Site

Getting Started

Storage

Features

Advanced Configuration

This page explains Advanced Configuration options available when editing a Site in Kontenum CDN. These settings allow you to fine‑tune delivery behavior, security, performance, and access control for your CDN site.

⚠️ Important: Changes may take a few minutes to propagate across the CDN network.

General Settings

Site Name

A human‑readable identifier for your site.

  • Used only inside the console
  • Does not affect traffic or DNS

CNAME Target

This is the system‑generated CDN endpoint for your site.

Example:

a0e78ae5870fe.kontenum.id

You must configure your Delivery Domain to point to this value using a CNAME record.

Added On / Last Modified

Informational timestamps showing when the site was created and last updated.

Delivery Settings

Delivery Domain

The public domain used by your end users.

Example:

cdn.example.com

Notes:

  • If left empty, Kontenum will automatically assign a default CDN domain
  • Must be a domain you own and can manage via DNS

Custom Response Headers

Add custom HTTP headers to responses sent to users.

Format:

Header-Name Header-Value

Example:

X-Frame-Options SAMEORIGIN
X-CDN-Provider Kontenum

Header Override Behavior

For certain standard headers, Kontenum will override the value returned by your origin if the same header is defined as a custom response header. This behavior prevents duplicated or conflicting headers in the final response.

The following headers are subject to override:

  • Content-Disposition
  • Content-Language
  • Access-Control-Allow-Origin
  • Access-Control-Allow-Headers
  • Access-Control-Allow-Methods
  • Access-Control-Expose-Headers

If any of the headers above are configured in Custom Response Headers, the value set here will take precedence over the value sent by your origin server.

Automatic HTTPS Protection (Let’s Encrypt)

Enable free SSL certificates issued by Let’s Encrypt.

How it works:

  1. Point your Delivery Domain to the CNAME Target
  2. Enable this option
  3. Kontenum automatically issues and renews certificates

✔ Certificates auto‑renew before expiration

Learn more about SSL Setup.

Origin Settings

Origin Type

Defines where content is fetched from.

  • Domain – External server or website
  • Storage – Kontenum Object Storage

Origin

The hostname of your origin server.

Example:

origin.example.com

Origin Path (Optional)

Restrict CDN delivery to a specific sub‑path.

Example:

/static/

Origin Protocol

Protocol used by CDN to connect to your origin.

  • HTTPS (recommended)
  • HTTP

Ensure this matches your origin configuration.

Request Headers to Origin

Custom headers added to requests sent from CDN to your origin.

Example:

X-Forwarded-Proto https
X-Custom-Origin-Header value

Security Settings

Geo Restriction

Restrict access based on user location.

Modes:

Example:

ID
SG

IP Restriction

Control access by IP address.

Modes:

  • Allow from list
  • Deny from list

Supports:

  • Single IPs
  • CIDR ranges

Example:

8.8.8.8
8.8.8.0/24

Referrer Restrictions

Allow or deny requests based on the Referer header.

Examples:

none
*.example.com
example.*

Secure Link (Signed URL Protection)

Protect content using time‑limited, signed URLs.

Components:

  • Secure Link Key (secret)
  • Hash name (default: md5)
  • Expiration timestamp
  • Optional extra arguments

Use cases:

  • Private downloads
  • Paid content
  • Anti‑hotlinking

See the built‑in modal documentation for full command examples.

Other Settings

Ignore Query Strings in Cache

Serve the same cached object regardless of URL query parameters.

Useful for:

  • Static assets
  • Cache hit optimization

Enforce HTTPS

Automatically redirect all HTTP requests to HTTPS.

Recommended when SSL is enabled.

Image Optimization

Automatically serves modern image formats (WebP / AVIF) when supported by browsers.

Disable if:

  • You require original image formats
  • Your application handles image negotiation manually

Cache Configuration

Kontenum respects standard HTTP cache headers returned by your origin server. This means you have full control over what content is cached and how long it remains cached at the CDN.

  • If your origin sends cache headers (such as Cache-Control or Expires), Kontenum will follow those instructions exactly.
  • If your origin does not send any cache headers (this does not include no-cache or no-store), Kontenum will still cache the content using a default cache duration of 30 days.

This default behavior ensures good performance out of the box while still allowing you to fine-tune caching behavior through your origin configuration.

Best Practices

  • Enable HTTPS + Auto SSL for all public sites
  • Restrict origins to HTTPS when possible
  • Use Secure Links for private or paid content
  • Avoid disabling cache by query strings unless necessary
  • Set appropriate cache headers at your origin for optimal CDN caching

Need help with advanced configurations? Contact our support team.