The delivery choices behind every media link.

The reference will be the same while the data associated with it has changed; therefore, existing pages, templates, or content management system (CMS) entries do not require a different URL. It is recommended that you review the replacement prior to making it public. Even though the address remains the same, dimensions, formats, animations, and/or meanings may have altered. Also keep in mind that browsers and intermediary cache devices can continue to contain older data. Therefore, make sure to employ proper re-validation or cache-replacement behaviors and confirm what users are receiving.

A CNAME record can point a hostname like cdn.example.com to a delivery provider, however, DNS is not sufficient to enable delivery. A delivery provider will need to verify the hostname, route its requests to the proper account/asset, and provide a valid TLS certificate so that HTTPS can be used. When testing the new hostname keep the current hostname active and when ready to cutover the embeds use a controlled cutover process.

Requests for access to files will no longer be authorized once the expiration date has passed, or when the authorization is revoked. The revocation of the authorization will not affect files that were downloaded prior to that point in time. Additionally, if the recipient had a cached version of the file, this version will continue to exist with its own lifetime, even after the original file's sharing page expires. When creating the access window for each file, make sure it allows enough time to complete the hand-off process. Provide clear instructions to all recipients regarding the expiration of their access to files. Test how the file appears to users after the file's sharing page expires, by attempting to view the file within a new browser session.

No. A referrer whitelist can discourage other websites from embedding your public files, however, the HTTP Referer header can be absent due to browser privacy settings or page policies, and non-browser clients can create their own headers. Additionally, it could prevent legitimate previewing of your files when the referring website's domain is not included in the whitelist. Authenticate users, use signed, time limited access for access control, and consider referrer checks as a means of controlling bandwidth usage rather than as a means of protecting confidential data.

Use a versioned URL if the page, build, legal record, or release must show exactly what was approved when it was. Use a stable mutable URL for content that will always show the most recently approved version (e.g., current prices, rotating banner). Keep a separate source/revision record so you can recreate earlier states.

The hosted-media roll out is currently being developed. We will provide detailed information on what type of files are supported, how to verify your CNAME and get your certificate and the specific ways in which the link control behaves. Each of these features will be added to this page as they become available. (Please make sure that you have properly tested all technical parameters, HTTP headers, MIME types, and browser requirements for modern desktop and mobile browsers prior to completing the deployment process).