Skip to content

Published Downloads ​

Published downloads give a file a permanent public URL on a cache node. Anyone with the URL can download the file without signing in to Ordyn.

Use published downloads to distribute an Agent installer, a configured Quick Support client, or another stored artifact. Each URL belongs to one cache node and has this form:

text
https://ordyn-cache.example.com/downloads/<id>/support.exe

Publish A Download ​

Under a cache node’s Published downloads, select the source file, a download filename, and an optional expiry. Sources include Ordyn releases, stored files, packages, OS images, and job artifacts. You can also publish from a managed file’s detail page.

Uploads follow the cache node’s synchronization windows and bandwidth limits. Wait for Published before sharing the URL. Without an expiry, the link remains available until it is withdrawn.

Edit Or Replace A Download ​

Edit a publication to change its source or expiry. The public URL and download filename stay the same.

A replacement can make the link temporarily unavailable while the new file is prepared and synchronized. A failed replacement can remain unavailable until the error is corrected. Retry the publication after correcting a synchronization problem.

A published release stays on the selected version until you edit it. Uploading a newer release does not change the selected version.

Disable, Expire, Or Delete ​

Disable a publication to withdraw its link while keeping the configuration, or delete it to remove the publication. Withdrawal takes effect when the cache receives the change.

An explicit expiry is enforced by the cache even when it cannot contact Ordyn. Disabling, deleting, or replacing a link requires communication with the cache. During an outage, the cache keeps serving its last applied downloads without an automatic time limit, subject to their expiry dates.

Published sources and required file content are protected from deletion and ordinary retention pruning, including while a link is disabled. Delete or retarget a source’s links and wait for the cache to apply the change before deleting the source. Delete all of a cache node’s published downloads before deleting the node. Transfers already in progress can finish.

Download Behavior And Hosting ​

Downloads use HTTPS and can be opened in a browser or fetched with a normal HTTP client. Interrupted downloads restart from the beginning; byte-range resume is not supported.

Choose a stable cache hostname before sharing URLs. Published URLs do not automatically move to a different cache node or hostname.