Repository navigation
2.9.0 — A Bowire that works behind the corporate proxy, signs in the Windows way, and keeps its cookies #761
thomas-stegemann
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A Bowire that works behind the corporate proxy, signs in the Windows way, and keeps its cookies
2.9 is the release for the network a company actually has. Bowire gets out through a mandatory proxy and trusts the CA a TLS-inspecting proxy signs with, calls intranet APIs as the signed-in Windows account, and keeps a session's cookies across calls, protocols and restarts — with a manager that shows them. Along the way SOAP and OData learned to send headers at all, and the site compares Bowire with the tools people are leaving. 2.9 includes every fix of 2.8.1.
Corporate networks
Proxy, bypass list and trusted CAs
Behind a mandatory proxy Bowire used to reach nothing: no connection it made knew there was a proxy (#680). Settings → Network now sets how outbound connections leave the machine — the system's proxy (
HTTPS_PROXY/HTTP_PROXY/NO_PROXY, else the OS settings), one proxy of your own, or none — with a bypass list in the forms people paste fromNO_PROXYand browser settings: a domain and its subdomains,.suffix, globs,host:port, IP ranges,<local>. Loopback always goes direct.A proxy that asks for credentials gets a user and a password reference —
keyring:service/accountorenv:VARIABLE— never the password itself, so no settings file, export or log holds one. A TLS-inspecting proxy re-signs every certificate; point Trusted CAs at its root (a PEM file or pasted PEM) and those chains validate. The bundle rescues exactly a chain error; a wrong host name stays an error, and the per-request "allow self-signed" stays the separate, unsafe switch it was.Settings apply globally or per workspace, the workspace winning field by field, and the host configuration wins over both:
--proxy-url,--no-proxyand--ca-bundlework on every command, andBowire:Network:*in appsettings or the environment. Check a connection on the settings page requests a URL with what is in force and says whether it got out, through which proxy, and why not — naming the missing CA or the proxy's demand for credentials. The MCP toolbowire.network.getreads the same.The proxy applies to REST, GraphQL, SOAP, OData, JSON-RPC, SSE, SignalR, WebSocket and MCP, and — in the standalone tool — to plugin downloads and the update check too. Some transports cannot use an HTTP proxy, and each plugin now says so: MQTT and NATS connect over plain TCP, a plaintext gRPC channel cannot tunnel, Pulsar's broker protocol connects directly. The settings page lists them, and a call that goes direct although a proxy is configured for its host is logged, so nothing appears to work around the proxy silently. Embedded in your ASP.NET app, Bowire leaves your application's own HttpClients alone.
Windows-integrated auth, NTLM and Digest
The .NET workbench could not call a .NET intranet API behind Windows authentication (#679). An environment's auth now offers Windows (Negotiate / Kerberos), which answers the server's challenge as the account Bowire runs as without a password; NTLM with explicit domain, user and password where Kerberos is not available; and Digest. Windows-integrated auth is offered only where Bowire runs on Windows; elsewhere the panel says why it is not there.
Digest is Bowire's own RFC 7616 implementation, because the platform's covers only
qop=auth: MD5 and SHA-256 with their-sessvariants,authandauth-int,userhash, and a retry on a stale nonce. NTLM credentials are offered only to NTLM and Negotiate challenges, so a server answering with Basic never receives the password. Each credential set gets connections of its own — NTLM authenticates the connection, not the request — and the schemes apply to REST, SOAP, OData, GraphQL, SSE, JSON-RPC, MCP and the SignalR and WebSocket handshakes. From the command line:bowire call --negotiate,--ntlm DOMAIN\user:password,--digest user:password.A cookie manager, and cookies beyond REST
The cookie jar was REST-only, lived in memory and showed nothing (#681). Each workspace now keeps a jar per environment in its
cookies.json: persistent cookies survive a restart, session cookies end with the process. The jar applies to every protocol over HTTP and to the WebSocket and SignalR handshakes — the upgrade is where a socket API usually decides who you are — matching domain, path,Secureand expiry as RFC 6265 does.Under Keep cookies in the environment's auth, the manager lists the jar by domain — name, masked value, path, expiry,
Secure,HttpOnly,SameSite— to edit, add, delete, or clear a domain or everything.bowire cookies list | clearand the MCP toolsbowire.cookies.listandbowire.cookies.cleardo the same from outside. The jars ride along in the workspace export, and a git-native workspace's.gitignoreleavescookies.jsonout. Cookie values are credentials: recordings and HAR exports mask them unless you switch that off.Behaviour change: without Keep cookies, Bowire now keeps no cookies at all. Until 2.8, a plugin's shared HTTP client silently kept whatever a server set and sent it back on later calls — across environments.
Fixes along the way
SOAP and OData send headers
SOAP and OData sent none of a call's metadata: an
Authorizationheader from Basic, Bearer or an API key never reached a SOAP or OData service. Both now send the headers — SOAP's four settings (soap_actionand the like) stay settings — and the challenge-response schemes above.The command line gets the same clients
Protocol plugins that were never initialised — which is every plugin in
bowire callandbowire test— used a bare HttpClient: no CA bundle, and now no proxy-aware, auth-aware routing. They use Bowire's own client everywhere.What 2.8.1 fixed
Internal plugin configuration no longer reaches a target as headers, history and recordings keep no credentials, and a locked server URL is enforced by the server — see the 2.8.1 notes, including which keys to rotate.
The site
Bowire and the alternatives
bowire.io/alternatives compares Bowire with Postman, Insomnia, Bruno, Hoppscotch, Scalar and Mockoon, one page each: when the other tool is the better fit, the rows where the two differ, and how to move over today (#671). Every fact comes from the one table the home page's comparison renders, so a correction lands on both. The changelog is built from these notes on every release, reachable from Downloads, and the site's internal link check checks something again and runs in CI (#755).
The full commit list, contributors, and compare-URL diff are auto-generated below.
Added
e553bb6)d247cb2)ec7a48a)5b9cc29)c5d0319)b145683)Fixed
f6d22b4)5d8b0ae)8dc0c27)de41f9b)b20745e)5a920d4)dc5e490)f93fdce)Documentation
bbb7bd0)d4bab7a)Other
da3c841)Maintenance — 12 maintenance commits
6b0a805)817d01d)942d2a5)9f996a1)bc92035)237a1fb)b076802)0e8b9ec)2.8.0#757) (433e98f)c29a3d6)bcb2dee)e9e0393)Contributors: Claude, Thomas Stegemann
Full diff: v2.8.0...v2.9.0
This discussion was created from the release 2.9.0.
All reactions