Tim Perry

Ah, I see, that makes sense. Yes, I think that's not really supported right now. You could try creating many rules each matching different sets of parameters and returning different...

> How about we have thenCallback support to return stream and where users will be responsible for writing to stream the way they wanted. I'm not sure exactly what you...

> Currently the thenCallback supports different options to return, e.g. json, body. What if we can return stream from there? We can prepare the stream within thenCallback and return like...

Hey @philsturgeon! I haven't dug into this any further, but I've just tested with the same code from above, and I can confirm it's still an issue: bundling the official...

Hi @H0r53, can you share an example that reproduces this issue please? I've just tested for myself by running: ``` curl -X GET -H'a: 1' -H'c: 2' -H 'b: 3'...

> my understanding is TLS fingerprinting should not be an issue if the agent is Chrome Unfortunately this is not true. HTTP Toolkit has a different TLS fingerprint to Chrome....

That makes sense, it does sound like this is a TLS fingerprinting issue in your case. It's always a bit of an unpredictable process of what gets blocks - it's...

I've just pushed an update with a few big improvements here @H0r53. HTTP Toolkit will update in the background next time you run it, within a couple of minutes, and...

If you hover over the HTTP icon in the top left, you can see the versions of the various subcomponents - things should be improved if you're using server 1.10.0+....

This will be due to flatpak sandboxing, because to detect browsers (and most other apps) HTTP Toolkit needs to be able to read & execute files from your whole file...