Using Edge Platforms with Public Hosting

Public Hosting lets you share files and directories via public URLs. By default, those URLs are served under the hosted-by-files.com domain. Files.com Custom Domains let you use one or more of your own hostnames while keeping the hosted URL paths.

An edge platform adds routing logic between your public URLs and the files hosted on Files.com. Use it for URL rewrite rules, content selection, or caching. You build and maintain the integration; Files.com continues to host the source files. Implementing URL Rewrites covers provider setup and handling links in hosted index pages.

Stable Download URLs

A software download link can stay the same while the release it serves changes. For example, an edge rule can map https://downloads.example.com/latest/installer.zip to https://example.hosted-by-files.com/releases/2.4/installer.zip.

When you choose a new release, update the rule to point to its file. Visitors keep using the same download link. Keep the versioned files available for people who need a particular release.

Shared Assets Across Brand Domains

Two brands may need different public paths for the same file. For example, https://brand-a.example.com/downloads/logo.svg and https://brand-b.example.com/press/logo.svg can both route to one file in your Files.com Public Hosting folder. Updating that source file updates the content served through both routes, subject to any caching you configure.

If only the hostnames differ, native Custom Domains already support multiple branded addresses. Edge routing is useful here because the paths differ too.

Regional Content

Regional URLs can select different files without exposing their storage paths. An edge rule can map https://eu.docs.example.com/manual.pdf to a file under /manuals/eu/, and the corresponding US hostname to a file under /manuals/us/.

Your routing rules determine which version visitors receive. Files.com stores and serves the regional files; it does not choose the region for this integration.

Caching Repeated Downloads

For files intended to be publicly available, such as software installers or product manuals, an edge cache can serve repeated downloads without fetching the file from Files.com each time. Cache hits reduce outbound transfer usage on your Files.com site.

Configure caching separately from URL rewriting. Choose a cache lifetime and a way to clear cached content when files or routing rules change, so visitors receive the version you intend to publish. Your edge provider's cache rules determine when requests return to Files.com.