Backends
HTTP(S)
A read-only filesystem source over plain HTTP and HTTPS URLs.
The http and https schemes are built in and need no configuration. They
expose a remote URL as a read-only source you can cat or cp from.
dumont cat https://example.com/data.json
dumont cp https://example.com/archive.tar.gz ./archive.tar.gzCapabilities
| Cap | Value | Why |
|---|---|---|
| RandomRead | ✅ (when the server supports it) | ranged GET via the Range header |
| Write / Append / Truncate | ❌ | read-only source |
| Directories | ❌ | a URL addresses a single resource |
| MTime | depends | from Last-Modified when present |
Notes
- Read-only. HTTP is a source, never a destination — using it as a
cpdestination is an error. - Ranged reads. When the server advertises range support,
ReadAtissues a ranged request so large files can be read in pieces; otherwise the whole body is streamed. - This backend is most useful as the source side of a cross-store
cp— pull a remote file straight into an object store or local disk.