Skip to content

Security

.http files, scripts and runbooks are code you run. Treat a repository or collection from someone else as you would any code: read what it does before sending its requests.

Pre-request scripts, response handlers, script files, and scripts imported from Postman or Insomnia run in a sandboxed JavaScript interpreter.

  • They can’t reach your files, start programs, load libraries or use .NET. Code a script downloads and runs with eval stays in the same sandbox. Request scripts are stopped after 30 seconds, with limits on statements and recursion.
  • They can read the values a request can use, including your private env file, OAuth tokens and client.global values, and send HTTP requests anywhere, including to machines on your network.

So the worst a hostile script can do is send your secrets somewhere, not harm your machine. A file’s # @reqjet.pre-request script runs before every request in that file.

  • >> path saves a response only inside the folder the requests are in. Anything outside it, such as ../ or an absolute path to a startup folder or shell profile, is refused, so a downloaded file can’t be placed where it would run later.
  • < path sends a file as the body. It’s shown in the request and on the Sent request tab, so check it before sending a request from somewhere else.
  • A request can send any value to any address, such as Authorization: Bearer {{token}} to someone else’s server. That’s visible in the request itself.

Reqjet only asks your system to open web pages: https:// and http:// addresses (and mailto: for links you click in a runbook). Other kinds of address, such as file: or special protocol handlers, could start a program, so a runbook link or an OAuth sign-in page using one isn’t opened. An OAuth Auth URL must be https://, or http:// to this machine for a local identity server.

The mock server only listens on this machine, only answers requests addressed to localhost, and only lets web pages served from this machine read its responses. Its responses can be real ones from your session, so other sites you visit while it runs can’t read them.

  • Secrets belong in the private env files (http-client.env.json.user or http-client.private.env.json). Reqjet offers to add them to .gitignore when it finds one a repository isn’t ignoring.
  • Secrets are masked on screen, and left out of HAR files (unless you choose with credentials) and diagnostic info.
  • Response history, OAuth tokens, cookies and prompt answers are kept in memory only, never written to disk.
  • Digest, AWS and Windows credentials are worked out when sending. The Sent request tab and HAR files show what was sent, not your password or secret key as written.
  • Your settings are per user, and never written into your folders.

reqjet run runs a repository’s scripts as the app does. In CI, point it at your own repository, not at one you haven’t checked.

Only the update check: at most once a day, release builds ask GitHub for the latest release. Turn it off in Preferences. There’s no account, analytics or tracking.