Support
Plainwire is supported through GitHub issues. Search the existing issues first; if nothing matches, open a new one. Questions, bug reports and feature requests are all welcome there.
Troubleshooting
“self-signed certificate” or “unable to verify the first certificate”
Since 0.2, add # @insecure above the request line to accept the certificate for that request, or set "plainwire.rejectUnauthorized": false in settings to accept it everywhere. Only do this for servers you control. A certificate signed by a locally trusted CA (for example one made with mkcert) avoids the problem altogether. Details: self-signed certificates, ports and proxies.
Requests behind a proxy
Since 0.2, set "plainwire.proxy": "http://user:pass@proxy:8080"; without it Plainwire uses VS Code’s http.proxy setting, then the HTTPS_PROXY / HTTP_PROXY environment variables. Hosts in NO_PROXY and localhost are sent directly. SOCKS proxies are not supported yet. If requests still fail, open an issue with your editor name and version and how the proxy is configured (without credentials).
Where is my history stored?
History of sent requests (the last 100 by default, setting plainwire.historySize) is kept locally in VS Code’s per-workspace extension storage, inside your editor’s user data folder (for VS Code on Linux that is under ~/.config/Code/User/workspaceStorage/; on macOS ~/Library/Application Support/Code/User/; on Windows %APPDATA%\Code\User\; Cursor, Windsurf and VSCodium use their own folder names). It never leaves your machine through Plainwire. To clear it, use the Clear History button in the History view. Your saved requests are not in history: they are the .http files in your workspace.
A variable shows up literally as {{name}}
- Check that an environment is selected and that it defines the variable, in
http-client.env.json,http-client.private.env.jsonor therest-client.environmentVariablessetting. - File variables (
@name = value) must be defined in the same file. - For chained values like
{{login.response.body.$.token}}, send the named request (# @name login) first.
My file does not appear in the sidebar
Collections list files ending in .http or .rest inside the open workspace folder. Files outside the workspace, or excluded by your editor’s file exclusion settings, may not be listed.
An import came out wrong
Thunder Client scripts are not imported. Postman test and pre-request scripts are kept as > {% %} / < {% %} blocks, except scripts on a folder or the whole collection, which are listed as warnings; a script that uses pm.sendRequest or require() is kept but those calls fail when it runs (what the pm API covers). If a request, header or body is missing or wrong, please report it with a minimal, secret-free copy of the exported file.
How to report a bug
- Update to the latest release and check the problem still happens.
- Open a new issue and include:
- the Plainwire version and your editor and version (VS Code: Help → About), and your operating system;
- the smallest
.httpsnippet, cURL command or import file that shows the problem; - what you expected, and what happened instead (the error message, or the response status);
- any errors from Help → Toggle Developer Tools → Console or the Output panel.
- Remove secrets first. Replace tokens, passwords, API keys, cookies and private hostnames with placeholders. Issues are public.
Security problems should not be reported in a public issue with exploit details; open an issue asking for a private contact channel instead, without the details.