![]() It also adds new constraints on the design of future features. I can see how it's useful in some cases, but doing this well enough for an official release at least means adding more logic to correctly detect this case and revamp the UI to show totally different interception options etc in that environment. It'd be pretty confusing to release an official Docker deployment mode that doesn't support intercepting Docker.Īll that makes me quite cautious about merging this in and officially supporting it myself, at least in the short term. Most notably this won't ever be able to intercept other Docker containers ( #1 - currently implemented but in beta) which requires lots of mechanisms that only work with the server running on the host, and that's a problem since this setup would have the same audience as Docker interception. AFAICT there's also no way any approach like this can ever support many HTTP Toolkit features correctly, due to Docker limitations, especially the various interception options, which is a really big part of the app. This approach is clever, but it does diverge quite a bit from how HTTP Toolkit normally runs, and creates a bunch of extra config settings to do so. Out of interest, why did you bundle the server as a separate directory, instead of using the version straight from npm? Oooh, interesting approach! Nice work still has the limitations above, in that you can't launch any intercepted applications from inside the Docker container, right? Not top of my list at the moment, but let's see if this gets many □ votes, and I'll keep it in mind for planning as I go. ![]() I played with this a little while ago and it works, the tricky part though is allowing the server to run headlessly, so the UI can connect & disconnect occasionally whilst and the server keeps happily running in the meantime. You do lose the ability to launch intercepted clients automatically on the target system (mostly for security reasons) so everything has to be configured to use the proxy manually, but for many cases that's a worthwhile tradeoff. With some small changes it's totally possible to run the server inside Docker and the UI outside, and use it just like a normal application whilst the proxy runs inside a Docker container, or on a remote machine in the cloud, or anywhere else that can run Node.js. HTTP Toolkit is composed of two parts: a Node.js proxy server and a web UI, which talk via a local HTTP API. There's actually some even more interesting options here though. If you're interested, give it a go, and do let me know if you have problems. ![]() Have you tried it? I haven't, but in theory if you run a desktop environment inside Docker you could run HTTP Toolkit in there no problem and with VNC everything should work straight away, no changes required. By linking the networking of the docker containers, all the other containers will route through the httptoolkit container.ĭoes 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. This can also relate to issue #1, to help with proxying docker containers between docker containers. If anything more, we can document what is needed. I'm hoping in terms of docker version, things mostly work out of the box without too much mucking around, maybe enabling some things for docker and exposing some ports. With this testable and working on Linux, Mac, Windows as the hosts. And maybe the community can contribute to this with a PR if I don't ever get to it. I could look into this myself, but thought it makes sense to put in official request. ![]() I'm thinking it would be useful to have a docker image of httptoolkit (Linux version) one can deploy via docker for use without installation on actual host machine, with the GUI aspects via X11 (and/or VNC?) from container to the host. I was researching online, and there are docker image offerings (not officially from the proxy developer/vendor though) of various inspector tool proxies like Charles, Fiddler, and non-tool proxies like Squid, nginx, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |