Scenarios

Transfer a file

Use Upload for basic uploads and Files to browse, inspect, download, or delete them. Upload can build Multipart, Raw URL, Raw Header, and No filename requests and can declare the file-part or raw-body MIME. No filename sends raw bytes to / so the server generates the name; it never sends raw bytes to /uploads.

Profile and method comparison support remains available internally, but its controls are currently hidden from the Upload interface. Use individual sends while refining a request; each send may create a file and trigger gateway inspection.

Start here when checking whether a gateway permits ordinary file transfer.

Exercise HTTP methods

Use Requests to send a method and inspect the status, headers, and body. The server advertises its active core methods through PING.supported_methods.

Test Advanced routing

An Advanced Session binds an immutable path prefix, decoder, and optional diagnostics to a bearer token. It accepts the documented payload carriers and can route an unregistered method such as SYNCDATA to an upload. Payload mode is explicit: none, XOR, or AES. See Advanced Sessions.

Exchange an encrypted note

Secure Notepad encrypts content in the browser and stores ciphertext on the server. The server does not retain the client-derived key. If the browser session key is lost, the old note cannot be recovered from the data directory.

Generate a transport artifact

SMUGGLE creates a temporary same-origin HTML, SVG, or XML artifact around an uploaded test file. Its URL is one-shot and may be consumed by a scanner, preloader, or HEAD request before the intended user opens it.

Provide temporary access

For a short authorized demonstration, use a loopback server behind the disposable SSH tunnel. For a service reachable from an untrusted network, use the public-direct procedure.