Orange Logic uses the Amazon CloudFront Content Delivery Network (CDN) to deliver content to external audiences quickly and reliably.
Cache options
Edge server location {#edge-server-location}
Amazon CloudFront has edge servers across the globe. We will configure your CDN to reach your region’s users. Refer to the Amazon CloudFront map to see the available edge server locations.
TTL and cache invalidations {#ttl-and-cache-invalidations}
The length of time for which asset formats are cached in the edge server is called the time-to-live (TTL). When assets are cached for a longer period of time, fewer users need to wait for the content to be served from the origin server. In contrast, cached assets might not reflect the most up-to-date content. The TTL needs to balance how quickly content can be served to end users with how up to date that content is. The default TTL is 24 hours. Submit a support request to adjust the TTL.
Manually refresh or revoke formats
When needed, users can manually refresh content via the public embed link API or in the My shared assets page. This means that the formats are removed from the edge server. When someone next accesses those formats via a public embed link, they access the updated content.
Automatically remove deleted assets
By default, deleted formats are stored in the cache for the full TTL, even if the original asset is deleted in Orange Logic during that time. When needed, users can manually revoke access to individual links from the My shared assets page. An Orange Logic specialist can configure the platform to remove formats derived from deleted assets immediately. Submit a support request to change your organization's TTL. You can also invalidate the cache for individual links.
CORS header
CDN links are public by default. The CORS header is Allow all sites (Access-Control-Allow-Origin: *). This is common for public resources.
Insight:Cross-Origin Resource Sharing (CORS) headers
CORS (Cross-Origin Resource Sharing) headers are a set of HTTP headers that allow a browser to request resources from a different origin, such as another domain, protocol, or port). By default, browsers block web pages from requesting resources from another domain. This prevents malicious websites from making unauthorized API calls or reading private data.
The
Access-Control-Allow-Originheader is the server’s way of explicitly telling the browser which origins are trusted. If this heading is missing or does not match the requesting webpage, the browser will stop the request.This header is used in various circumstances, including a public API or files hosted in a CDN.
The
Access-Control-Allow-Originheader lets you:
- Allow access to just one site (
Access-Control-Allow-Origin: https://app.example.com)- Allow multiple specific sites (usually handled dynamically by echoing the
Originheader if it’s in an allowed list)- Allow all sites (
Access-Control-Allow-Origin: *). This option is common for public resources, such as fonts and open APIs.
Set the CDN name, custom domain, and custom URL pattern
An Orange Logic specialist can change the name of your CDN in the link. You can also set a base URL for custom embed links that users create on an asset-by-asset basis. This replaces the default base URL. For example, let’s say that you want custom embed links to include the text “public,” an asset’s identifier, and a user-created name:
https://mango-atelier-cdn.orangelogic.com/mango-atelier/[asset-identifier]/[CUSTOM_LINK_NAME]
When users select the custom link options when they generate the link, they enter custom text, and it replaces [CUSTOM_LINK_NAME] in the link pattern.