Nodekeeper's own entry service for ports 80 and 443. In the panel it is called "CDN sites", and it is included from the Personal plan. It sits in front of your website and handles caching, origin fetching, rewrites and traffic rules; the bandwidth and servers are your own. For what it can do and who it suits, see the self-hosted CDN page.
What you can set when creating a CDN site
- Cache: per-path (*.html, *.css, *.js and so on) TTL, maximum file size, methods and status codes; build the cache key from the query string, Host, client IP and User-Agent; set the log retention in days.
- Stale copy when the origin fails: the copy cached earlier is served when the origin returns 5xx or times out; the permanent-fallback switch serves the cache whenever one exists.
- Several origins and a backup origin: a dead origin is taken out automatically and put back when it recovers.
- Response content replace: swap given text in responses for other text, for example an old domain for a new one.
- Security tab: bind WAF rule sets, IP / CIDR rule sets, GeoIP rule sets and JA3 / JA4 fingerprint lists.
The WAF is not on by default
A new CDN site does not go through the WAF until you tick at least one WAF rule set on the site's Security tab. Some installers (the WordPress and Discuz setup wizards, for example) trip rules, so you can untick the rule set while installing and tick it again afterwards. See WAF.
Related features
- JA3 / JA4 TLS fingerprint protection, IP / CIDR rule sets, GeoIP rule sets
- Sync groups: share rules, CDN sites and forwarding settings across edge nodes (Business)
- Website analytics: CDN sites share one list with your other sites