Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

When app starts, I get an error and app exits.

My platform is Windows 7 64bit. My account has restricted access.

But app starts ok when I run it as admin.

Maybe, related to #19

If app doesn't work with restricted user accounts, it should be mentioned elsewhere, I think.

It would be useful to be able to filter the exchange list more precisely, not just by simple text matching. Some suggested filters:

• By URL/host
• By specific headers
• By body contents
• By status
• Negated filters for the above
• By label/tag (with some kind of exchange-tagging system)
• By source

Any other ideas?

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 take a look & vote on the most popular ideas so far.

The initial hex editor is ok for basic viewing of hex data, but doesn't provide many other features, such as automatic ASCII decoding, showing the address of each byte, or editing hex data (in breakpoints or on the mock page).

In some use cases (e.g. protobuf data until #80 is fully supported) raw binary data is used heavily in APIs, where this could be very useful.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

macOS 10.14, latest Chrome.

Installed HTTP Toolkit, started a "Fresh Chrome", works great, fantastic tool.

Now when other apps start a fresh Chrome, and HTTP Toolkit is not running, I get a 'no internet' / proxy error.

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 take a look & vote on the most popular ideas so far.

I thought this tool would be useful for testing a new CDN; I've been looking for something that I can hand to business users or other folks that aren't super technical. I purchased the Pro version and setup a simple Mock rule to forward requests for www.ni.com to the new CDN's CNAME, www.ni.com.cdn.cloudflare.net. That worked, sort of; the problem is that it also updates the HTTP request's Host header, which created a request that is broken.

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 take a look & vote on the most popular ideas so far.

For HTML content, it can be useful to see the full rendered page that the response represents. It would be useful to have this as a body rendering option.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Hello, the tool visually looks nicer than the built-in debug tools included with browser. However, can you please point out any differences between this and the built-in tool? I see nice color coding of the response body, but what else? Maybe a comparison checkbox between your tool and what is available in Chrome, Firefox, Safari, Edge, etc.

Thanks and keep up the great work!

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 take a look & vote on the most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

Is it possible to use a client certificate with HTTPS? This is something fiddler supports, but I can't seem to get it working with Http Toolkit.

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 take a look & vote on the most popular ideas so far.

Firstly, congrats on the product, @pimterry, I had a good first feeling while testing it.

This is my suggestion, adding somewhere around here a button to automatically copy request/response body to clipboard.

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 take a look & vote on the most popular ideas so far.

If an HTTPS client connects to HTTP Toolkit, but rejects the certificate and so never sends a request, currently HTTP Toolkit shows nothing.

With a few small changes, we could report & include these requests, and at least show the host they were trying to talk to (but of course not any of the other details, since the request is never sent).

This might be useful to debug manual interception setup, or to detect clients that are explicitly pinning their own certificates, and thereby rejecting HTTP Toolkit's interception.

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 take a look & vote on the most popular ideas so far.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

The application crashes on startup (immediately after the loading progress bar) with this error message:

Server crashed with 'Error: Conflict on chrome.channel: "stable" !== "dev"' (1).

(that error toast disappears almost instantly, took a few tries to get a screenshot of it)

The message looks correct in that I have Chrome Dev channel installed.

Does HTTP Toolkit only support the stable Chrome channel?

• Windows 10 Pro x64 - Version 1903 - Build 18362.356
• Chrome Dev - Version 79.0.3921.0 (Official Build) dev (64-bit)

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 take a look & vote on the most popular ideas so far.

I'm using Mac OS X El Capitan 10.11.6 and this is the scenario on app ready:

It doesn't see any browser.

Hi Tim, Jake here! Not sure if you remember me from your Softwire days :)

I've just downloaded the latest version of HTTP Toolkit for WIndows from your website (HTTP.Toolkit-0.1.14.Setup.exe), and I don't seem to be able to find the mock option:

Not sure if there's something simple I'm missing or not - let me know if you'd like any more info.

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 take a look & vote on the most popular ideas so far.

Hi!

I am just trying out your tool. It installed correctly, but when it launches, I get the following dialog:

HTTP Toolkit hit an error
Server crashed with 'Error: Conflict on chrome.bitness: 32 !== 64' (1).
Please file an issue at github.com/httptoolkit/feedback.

It will then restart and attempt again and crash again a few more times.

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 take a look & vote on the most popular ideas so far.

By default, HTTP Toolkit defaults to 8000, and increments that if that is not available until it finds a port that is free.

Sometimes other applications require port 8000 though, so this isn't perfect. For those cases, it would be useful to allow configuration of a specific port.

What should happen if you configure a specific port, and that port isn't available on startup?

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 take a look & vote on the most popular ideas so far.

I only have Chromium and Firefox-Nightly installed on my system.

Chromium is not supported by "Fresh Chrome": Error: chrome is not installed in your system.
Firefox-Nightly is not supported by "Fresh Firefox": Error: firefox is not installed in your system.

Hello, I install HTTP Toolkit on my Windows 7 professionnal computer.
This computer is protected by company security policies but I'm admin of it and I can install software or open port in the firewall.
When I launch it, I have this error message (who appears less than 1s...) :
HTTP Toolkit crashed
Server shutdown unexpectedly with code 1.
Please file an issue at github.com/httptoolkit/feedback
I doesn't found log or other information who can explain this error.
Is it possible to activate more debug log ?
Thanks.

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 take a look & vote on the most popular ideas so far.

In addition to #48, a useful extension would be to send fuzzed requests.

I.e. not just send this one request, but define a request generator that sends a bunch of different requests, trying different edge cases, to see what happens and find bugs/security issues.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

regenerate ?

beacuse a CA key may leaked, or I just want a new one.

import ?

beacuse I want share CA key with other http proxy app on iOS (do not want too many self issued keys)

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

Make it possible to somehow intercept & examine traffic from CloudFront, or reverse proxies like Varnish and Nginx.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Hi Tim,

Thanks for this tool. I just download the .deb file, but I can't test it on my computer because the application crash after display the main windows.

Log output :

$ httptoolkit
undefined:28
}}
 ^

SyntaxError: Unexpected token } in JSON at position 662
    at JSON.parse (<anonymous>)
    at /usr/lib/httptoolkit/resources/app/httptoolkit-server/node_modules/@james-proxy/james-browser-launcher/lib/config.js:35:34
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:408:3)
undefined:28
}}
 ^

SyntaxError: Unexpected token } in JSON at position 662
    at JSON.parse (<anonymous>)
    at /usr/lib/httptoolkit/resources/app/httptoolkit-server/node_modules/@james-proxy/james-browser-launcher/lib/config.js:35:34
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:408:3)
undefined:28
}}
 ^

SyntaxError: Unexpected token } in JSON at position 662
    at JSON.parse (<anonymous>)
    at /usr/lib/httptoolkit/resources/app/httptoolkit-server/node_modules/@james-proxy/james-browser-launcher/lib/config.js:35:34
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:408:3)
Failed to start server, exiting. Error: Server shutdown unexpectedly with code 1.
    at Promise.then (/usr/lib/httptoolkit/resources/app/src/index.ts:149:31)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Some information about my Ubuntu version :

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

$ uname -r
 4.15.0-43-generic

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 take a look & vote on the most popular ideas so far.

A large number of HTTP Toolkit users are from non-English-speaking countries. It's likely that many software developers speak English anyway, but to varying degrees, so HTTP Toolkit is likely to be easier to use for many developers in their native language.

There is an open question of which languages to translate to first. Please post below if you have any suggestions!

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Currently these appear as 502s, if the proxy fails to connect upstream, but we could more closely emulate real errors, and show that in the UI more clearly.

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 take a look & vote on the most popular ideas so far.

I'm loving HTTPToolkit, nice work!

One of my main use cases is inspecting/troubleshooting WebSocket connections. Any plans to support WebSockets in the future?

The current crop of WebSocket cli clients and browser extensions aren't great, so I think a high quality tool like HTTPToolkit would be very successful.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

I have tested the master branch of httptoolkit-ui, with a terminal launched from http://local.httptoolkit.tech:8080/intercept.

$ curl --http2-prior-knowledge https://nghttp2.org
curl: (16) Error in the HTTP2 framing layer

Supporting HTTP/2 with prior knowledge would be important for traffic interception on Android, several Google services are connecting with HTTP/2 directly.

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 take a look & vote on the most popular ideas so far.

Proxying of exchanges should continue happily for the intercepted device, it's just that the exchanges themselves shouldn't be recorded or visible in the UI.

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 take a look & vote on the most popular ideas so far.

The standalone version cannot be loaded because there is no electron compiler, as this message indicates.

My system is Windows 10 1809 up to date (17763.253).
I've tried put it another place to avoid space in the path, but the error still exists.
Do I need install something beforehand?

Many clients send base64-encoded content, either in the body of the response or the header values. It would be useful to have an easy way to decode this.

Unclear what format this should take, since we can't easily tell when it's required...

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 take a look & vote on the most popular ideas so far.

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 for yourself too.

Lots of potential more complex options here (post any ideas below!) but a simple initial version plus a "rerun request" button next to intercepted traffic should be easy & immediately useful.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Using "Fresh Chrome" option on macOS:

When accessing a local development site that has a self-signed certificate (which is trusted in the system keychain), we see the error "Error: unable to verify the first certificate".

Let me know what other information I can provide.

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 take a look & vote on the most popular ideas so far.

Header data is presented in a fairly raw form right now. There's a lot we could do with this (e.g. splitting out cookie data by cookie, highlighting key headers like Location of 30X responses). Ideas welcome, and I'd love to hear about the headers that are most important to you, and how you'd like to see them.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

Worked great for several days. Suddenly the "Fresh Firefox" option is labeled not available, and when I click it, Debug tools state that it is not installed. It most certainly is.

vendors~main.bundle.js:70 Error: Server error: Unexpected error value: "firefox is not installed in your system." at activateInterceptor
    at f (app.js:1)

Same results on 2 machines.
Windows 10 Pro, Firefox developer edition

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 take a look & vote on the most popular ideas so far.

Does this work with NVM?
I notice you override node, I get usage: dirname path and nothing is executed when I am trying to run my node application. Node/NPM commands give this.

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 take a look & vote on the most popular ideas so far.

Currently, HTTP Toolkit will reject self-signed or otherwise invalid certificates from the upstream site.

In many cases, devs use self-signed certificates locally, so this can cause problems. As a workaround, you can run the app with certificate verification completely disabled by setting the env var NODE_TLS_REJECT_UNAUTHORIZED to 0. E.g. on Linux:

export NODE_TLS_REJECT_UNAUTHORIZED=0
httptoolkit

A proper solution to this is doable though... Probably by forwarding on certificate issues (e.g. bad hostnames, expired certificates) so they appear in the certificate your browser/client sees and you can handle them as normal, and by signing intercepted but untrusted certificates with our own untrusted CA, to simulate that behaviour too.

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 take a look & vote on the most popular ideas so far.

HTTP Toolkit could allow you to pause requests before they're sent, or responses before they're received by the client, and manually edit them before they're sent on.

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 take a look & vote on the most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

For both HTTP Toolkit and Mockttp. Somewhat related to #32.

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 take a look & vote on the most popular ideas so far.

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 take a look & vote on the most popular ideas so far.

HTTP Toolkit could automatically detect & decode gRPC/gRPC-web.

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

As of just now, you can mock & rewrite traffic, using the set of matchers & handlers available on the mock page. You can do a little dynamic logic there by forwarding matching requests to your own local server, which can include whatever logic it likes, but that is still a quite limited form and makes rewriting of remote responses, among other things, very challenging.

Unfortunately, embedding a scripting language inside HTTP Toolkit is quite limiting. Do you have to edit it inside the app? Can you use external packages and data stores? Do you have to use a specific language, that a significant subset of users probably won't already know?

It would be good to find a way to allow scripting, whilst avoiding some or (in a perfect world) all of these limitations.

If you're keen on this feature, context of how you'd use it would be super helpful. Please comment below to describe the kind of scripts you'd like to write!

Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.