Scaleflex DMO allows you define transformation rules based on image path and filename pattern matching. Rules allows you to apply default transformations on assets based on the asset’s filename.

This rule will apply the transformations - h=300&w=300&wat=1 for all image urls which contains .png string in their filename.

Presets:

You can create custom transformations using presets to shorten the Scaleflex DMO urls. If you wish to apply the same transformations on many images, you can define presets and apply transformations only using the preset name (X). Presets are used to shorten Scaleflex DMO delivery URLs and also used for generating dynamic asset transformations upon upload.

Example: //your-token.cloudimg.io/original_image_url/image.jpg?h=100&w=400&func=crop to be replaced by //your-token.cloudimg.io/original_image_url/image.jpg?p=car_x

Aliases:

Aliases can be used to shorten your Scaleflex DMO delivery URLs and hide parts of the asset folder path. Aliases must be prefixed and suffixed with underscores.

Example: //your-token.cloudimg.io/http://sample.li/image.jpg to be replaced by //your-token.cloudimg.io/_dmo_sample_/image.jpg

Please note that all aliases have to be unique for your account - aliases set in the alias section cannot be used in the Storage sections.

Due to the specific way aliases are matched, it is required to use only specific aliases that are not contained in part of other alias strings.

Example: If you define an alias _dmo_sample_ then you should not have:

• _dmo_

• _dmo_one_two_

• _my_dmo_one_

External domain whitelisting:

You can whitelist specific domains in order to allow only specific external sources to be requested. In addition, you can combine Domain whitelisting with Aliases above to send custom headers to an non-public external storage for authentication purposes.

In order to whitelist a specific domain, you need to enter the domain name without https://

Here, domain sample.li is whitelisted. Which means that if we try to process an image with any other domain except sample.li (eg: www.your-own-domain.com), it will return a HTTP 406 (Not acceptable) error.

However, this response can be changed to HTTP 404 (Default missing image)

CNAME or canonical name in Scaleflex DMO is used to replace your-token.cloudimg.io with your own domain name.

Example: //your-token.cloudimg.io/original_image_url/image.jpg to be replaced by //your-own-domain-name.com/original_image_url/image.jpg

Add one or multiple custom domains to deliver DAM assets over your subdomains, for example medias.acme.com. Once the custom domain added, you will need to create 2 DNS CNAME entries to validate the TLS certificate and point your subdomain to Scaleflex DMO.

Example:

• DNS1: _076f48ef8df3a3ca368b89c6f0bb0bcf.medias.acme.com. CNAME _29163927834ee4c4e03c365fd7282c74.nhqijqisfx.acm-validations.cdnprovider

• DNS2: medias.acme.com CNAME token.cdnprovider.com

Caching accelerates the loading times of images as it allows to host them as close as possible to your end users. By caching, your ensure maximum performance of your website.

When this cache expires, the image will be requested from the origin and the new image delivered to the client.

Please note that these settings can be changed upon request via a

Browser cache expiration interval (Max-age): The time in seconds that the image is allowed to be re-used. For instance, max-age=86400 indicates that an image remains in the browser cache for the next 86400 seconds (24 hours).

CDN cache expiration interval (S-maxage): S-maxage = 31536000 indicates that the image remains in the CDN cache for 31536000 seconds (1 year)

Automatic origin image refresh: If you need to use a very small caching interval for a specific image (for example, snapshots from a live webcam or a specific chart with dynamically changing contents), you need to change the Automatic origin image refresh setting in your Admin console. This tells our resizing servers to update all origin images after this interval has expired.

In Scaleflex DMO, a delivery URL is the generated link that allows users to access and retrieve optimized images or media files. This URL typically includes parameters that dictate how the image should be processed, transformed, or served.

//your-token.cloudimg.io/original_image_url/image.jpg

We can make various changes in this delivery url.

1. CNAME

2. URL format (Presets and Aliases)

3. Rules

4. Security

5. Caching

6. Default behaviours

If the original image is missing or the original image url is not accessible, you can define what default image to show to the end user who is trying to access the url.

You can also select the type of response:

1. HTTP 200 with default image

2. HTTP 200 with transparent 1x1 px GIF (V7 API only)

3. HTTP 404 with default image

4. HTTP 404 with empty image (body = 0 bytes)