Tim Perry
Tim Perry
There are a few Node.js modules for which HTTP Toolkit needs special hooks to configure for interception before they're used, as you can see here: https://github.com/httptoolkit/httptoolkit-server/blob/main/overrides/js/prepend-node.js. These are hooked correctly...
Would be useful to have something like Postman built-in, so you can send requests (intercepted & recorded automatically). Useful for resending other intercepted requests, and manually testing out API queries...
Support rules that take a matching string (or regex?) and a target, and perform an automatic search and replace over the body content. --- _Does this affect you too? Click...
If you create a "Pause the request & response to manually edit it" rule (or just a request or response equivalent), any time a matching new request is received HTTP...
In some cases, it's useful to have a persistent debugging proxy, where the UI is attached remotely and intermittently, while the proxy continues running indefinitely. This often (but not always)...
--- _Does this affect you too? Click the +:smiley: icon in the top right and add a :+1: on issues to help decide where HTTP Toolkit goes next, or [go...
By default, on Windows the HTTP Toolkit 'Fresh Terminal' option opens Git Bash as the terminal if present, or a normal windows `cmd.exe` window if not. Meanwhile 'Existing terminal' isn't...
It would be helpful if cookies sent with requests were viewable in an easier way, rather than the current raw string format. Probably easiest to parse them into a KV...
If you could export rules from HTTP Toolkit (as `.htkrules` files) and then import them into a Mockttp script (something like `mockServer.loadRulesFromFile('.../file.htkrules')`), then HTTP Toolkit would instantly become a visual...
In addition to #176 (showing which rule matched a request) it would also be useful to be able to see the original & transformed versions of request & response data....