Content Delivery Network (CDN)
Using a CDN allows your pages to load faster and helps provide a pleasant browsing experience for your visitors.
A Content Delivery Network (CDN) is made of geographically distributed servers and ensures fast delivery of the static resources of your Web pages (JavaScript files, CSS files and images). Caching static resources reduces the load on the Web servers and thus the bandwidth required by your applications.
Artifakt offers a CDN for all environments. The content of your websites can be distributed in more than 200 cities in 95 countries, as close as possible to your visitors.

Features and Optimizations

  • Smart CDN cache (TTL)
  • Geolocation (visitors' country code can be captured by your application)
  • Image optimization (Webp)
  • Mobile loading optimization (for Cellular Networks)
  • Smart load balancing (more details here)
  • Fast network with compression & custom-tuned TCP optimization
  • A static version of your pages is cached in case your servers go offline

Limits

The maximum file upload size and cached file size is 512MB. Artifakt only caches according to the file extension (and not according to the MIME type).
HTTPS requests sent to your application should run in less than 600 seconds or 10 minutes (hard limit, cannot be changed). If not, Artifakt will display an error page indicating that your website is not reachable at the moment.

Which file extensions are cached by default?

Artifakts CDN only caches the following file extensions by default:
class
eot
jpg
pict
svg
webp
css
eps
js
pls
svgz
woff
csv
gif
mid
png
swf
woff2
doc
ico
midi
ppt
tif
xls
docx
jar
otf
pptx
tiff
xlsx
bmp
ejs
jpeg
pdf
ps
ttf
Artifakts CDN doesn't cache HTML by default. If you need to cache HTML, please contact our Support team.

How the Cache Works

Artifakt caches static resources according to where your visitors come from and how often they access these resources.
A new copy of the resource will be cached and distributed each time the query parameters differ. For example example.com/mycar.jpg?param=query and example.com/mycar.jpg?param=query&param2=query will fetch the resource from your server but cache it under 2 different keys.
Please also note that the query parameters are not sorted before retrieving a cached resource. If a user runs the query example.com/mycar.jpg?title=test&portrait=0&color=0000 and then another user runs the query example.com/mycar.jpg?color=0000&portrait=0&title=test, then we will fetch the resource again even though we actually have the cached resource.
You can customize the behavior of the cache using the Cache-Control HTTP header, and more precisely the max-age directive (in seconds). This directive indicates that the HTTP response should be considered expired when it is older than the specified number of seconds.

Purge the Cache

If you are working on a development environment or have a particular need for your production environment, go to Environment β†’ Settings β†’ Domains to empty the CDN cache of all or part of your domains.
Purging the CDN cache
Last modified 1mo ago