Skip to content

Files

The Files page holds files kept on the server, and controls which of them are served over HTTP by a listener.

The files table

  1. Search - filters by file name
  2. Show all - switches between every stored file and only the ones that can be hosted
  3. Add file - uploads a file to the server
  4. Refresh - re-reads the list from the server
  5. File row - one stored file, with the hosted URLs it is currently served at

Stored and hosted

Two different things, on one page:

  • Stored - the file is on the server. Files arrive here by being uploaded from this page, and by being fetched from a host by an agent.
  • Hosted - the file is also reachable over HTTP, at one or more paths, through one of this server's HTTP listeners.

The toggle in the toolbar switches between showing everything and showing only the files that can be hosted.

Hosting a file

The hosted URLs action on a row registers a path on an HTTP listener. One file can be hosted at several paths at once, on different listeners, which is how the same file is served over two different routes without being uploaded twice.

Removing a hosted URL stops it being served. The file stays on the server.

Files an agent brings back

Anything an agent retrieves from a host lands here rather than in your browser. That is what makes it available to the whole team, and it is why a large transfer does not depend on your session staying open. The File Browser is the usual way to start one.

Housekeeping

Nothing on this page expires by itself. At the end of an engagement the stored files are part of what has to be cleaned up, and the hosted URLs are worth checking separately: a path that is still registered on a running listener is still being served, whether or not anyone remembers putting it there.