Merge pull request #265687 from iblech/patch-test-socks

    networking.proxy.httpsProxy = "http://localhost:8118";

  };

  nodes.machine_socks4  = { ... }: { services.privoxy = { enable = true; settings.forward-socks4  = "/ 127.0.0.1:9050 ."; }; };

  nodes.machine_socks4a = { ... }: { services.privoxy = { enable = true; settings.forward-socks4a = "/ 127.0.0.1:9050 ."; }; };

  nodes.machine_socks5  = { ... }: { services.privoxy = { enable = true; settings.forward-socks5  = "/ 127.0.0.1:9050 ."; }; };

  nodes.machine_socks5t = { ... }: { services.privoxy = { enable = true; settings.forward-socks5t = "/ 127.0.0.1:9050 ."; }; };

  testScript =

    ''

      with subtest("Privoxy is running"):

          machine.systemctl("start systemd-tmpfiles-clean")

          # ...and count again

          machine.succeed("test $(ls /run/privoxy/certs | wc -l) -eq 0")

      with subtest("Privoxy supports socks upstream proxies"):

          for m in [machine_socks4, machine_socks4a, machine_socks5, machine_socks5t]:

              m.wait_for_unit("privoxy")

              m.wait_for_open_port(8118)

              # We expect a 503 error because the dummy upstream proxy is not reachable.

              # In issue #265654, instead privoxy segfaulted causing curl to exit with "Empty reply from server".

              m.succeed("http_proxy=http://localhost:8118 curl -v http://does-not-exist/ 2>&1 | grep 'HTTP/1.1 503'")

    '';

})