CDN Performance mode
Direct S3 upload/download via presigned URLs (default ON). Proxy mode enforces speed/resume limits on the main app.
CDN Performance mode
Choose direct CDN traffic vs proxying bytes through the main app.
Where to find it
Admin → Servers → add/edit CDN (/admin/servers/add?cdn=1) → Performance mode → Direct upload and download (bypass main server)
Field: adminConfig.performanceMode. Default ON when unset (legacy rows included).
How it works
| Mode | Behavior |
|---|---|
| On | Browser uses S3 presigned PUT (upload TTL 86400 s) and GET redirect (download TTL 900 s) |
| Off | Bytes proxy through the main app (better metering; more main-server load) |
On the direct path these limits are not fully enforced: download/upload speed, resume, and simultaneous downloads. Download bandwidth is charged as the full file size when the download starts (cancel mid-download still counts full size).
This is separate from remote-node Performance mode (directDownloadEnabled, off until checked). Browser PUTs still need bucket CORS when Performance mode is on.
Common problems
Limits ignored on CDN
Expected when Performance mode is on - turn it off if you need proxy-enforced caps.
Direct upload URL could not be created
Verify CDN credentials and bucket CORS.