All spotlights

Product spotlight · March 2024

Turn on HTTP/3 and choose a shield region near your origin

You can now turn on HTTP/3 for each project, choose the shield region in front of your origin, and serve video and audio files with range requests.

Updated Global CDN For government and enterprise

What changed in March 2024

The March 2024 changelog has the full details.

  • HTTP/3 for projects

    You can now turn on HTTP/3 (QUIC) in each project's settings. The setting applies to all of the project's domains, so browsers that support HTTP/3 can connect over the newer transport.

  • Shield region selection

    Each project now uses a shield region that matches the project's own region by default, instead of a single US-West shield. You can change it in the project's advanced settings to Australia (Sydney), Europe (Frankfurt) or US-West (California).

  • Range requests for video and audio

    Static files now support HTTP range requests, so media players can request part of a file instead of the whole file. Files with common extensions, such as .mp4, .mp3 and .pdf, now default to the matching content type when none was stored.

Also from February 2024

The February 2024 changelog has the full details.

  • Cache key purging

    You can now purge cached content by cache key, as well as by URL or path, from the dashboard purge form or the API. One purge request invalidates every object that shares the key.

  • Brotli compression

    Each project can now compress its content with gzip (the default), Brotli with gzip fallback, or no compression. Set it in the project's advanced settings. It applies to text-based content, such as HTML, CSS and JavaScript, and only when the browser supports it.

  • Large file delivery

    Asset delivery now streams files to visitors as they are read from storage. Large files are served incrementally and delivered more reliably.

Who it is for

  • Origin owners

    Choose a shield region close to your origin, so your origin gets fewer requests and cache misses have less latency.

  • Sites with media

    Serve video, audio and other static files in parts, so media players request only the part of a file that they need.

  • Site developers

    Have your origin tag related pages with a shared cache key, then purge all of them with one request when they change.

How it works

A shield region sits between the edge locations and your origin. When an edge location does not have a file in its cache, the request goes through the shield region before it reaches your origin. This reduces the number of requests to your origin. A shield close to your origin also reduces latency on cache misses.

Before March, every project used a single US-West shield. Each project now uses the shield region that matches its own region by default. If your origin is in another region, change the shield in the project’s advanced settings.

HTTP/3 is a project setting, not a domain setting. When you turn it on, it applies to all of the project’s domains.

Range requests help with video and audio files. Responses now tell browsers that range requests are supported. A media player can then request one part of a video or audio file instead of the whole file.

February added cache key purging. To tag a response, your origin sends its keys, separated by spaces, in the Cache-Keys response header:

Cache-Keys: <key> <key> <key>

A purge request for one of these keys, from the dashboard purge form or the API, then invalidates all of the objects that carry it.

March also fixes two delivery problems. Custom 404 pages published at the /_quant404 route show again for missing and unpublished paths. Pages and files whose links percent-encode characters in the path, such as %3A for a colon, now load.

Get started

  1. Turn on HTTP/3

    In your project's settings, turn on HTTP/3 for all of the project's domains.

  2. Check your shield region

    In advanced settings, choose the shield region nearest your origin.

  3. Choose a compression

    In the advanced settings, choose gzip, Brotli with gzip fallback, or none.

  4. Purge by cache key

    Tag responses with Cache-Keys. Read Using cache keys.

Related: Explore Global CDN · Documentation · March 2024 changelog

Ready to try it on Quant?

Use the global CDN on your own project, or talk to our team first.