Mitmproxy/mitmdump multiple processes using same proxy port

mitmj · October 18, 2019, 7:48am

Hi.

I noticed that it is possible to run multiple mitmproxy/mitmdump instances on the same proxy port.
As I don’t think that this is a valid scenario (as it is totally indeterministic which process processes a request) so why doe mitmproxy not lock the used TCP port so that the second and third instance is getting an error - or is there an option to enable such a behavior?

Edit: I noticed that this behavior is hard-coded and cant be changed without modifying the code:

github.com

mitmproxy/mitmproxy/blob/e74e97bcd96346a1ae8c372a94149100a755739a/mitmproxy/proxy/server.py#L36


        pass


    def serve_forever(self):
        pass


    def shutdown(self):
        pass




class ProxyServer(tcp.TCPServer):
    allow_reuse_address = True
    bound = True


    def __init__(self, config: config.ProxyConfig) -> None:
        """
            Raises ServerException if there's a startup problem.
        """
        self.config = config
        try:
            super().__init__(
                (config.options.listen_host, config.options.listen_port)

Topic		Replies	Views
Starting mitmproxy as subprocess help	0	1285	June 18, 2019
Setting second proxy for libmproxy help	4	1628	May 10, 2017
Cannot tcpdump traffic with transparent mode on local machine help	0	1586	June 3, 2019
Test scenario with multiple clients needing the same "live" data help	0	610	July 20, 2018
Mitmproxy with Nginx help	1	2740	October 27, 2019

Mitmproxy/mitmdump multiple processes using same proxy port

Related Topics