Open Source Mac Proxy Clients - Page 2

the PiMP is an open-source, GUI, MCCP proxy client. It's intended to be simple to configure and hassle-free to use.

https://github.com/bentonstark/starksoft-aspen https://www.nuget.org/packages/starksoft.aspen

A lightweight Node.js private proxy registry. Verdaccio is a simple, zero-config-required local private NPM registry. No need for an entire database just to get started. Verdaccio comes out of the box with its own tiny database, and the ability to proxy other registries (eg. npmjs.org), also introduces caching the downloaded modules along the way. For those who are looking to extend their storage capabilities, Verdaccio supports various community-made plugins to hook into services such as Amazon's S3, Google Cloud Storage or create your own plugin. If you want to use all benefits of npm package system in your company without sending all the code to the public, and use your private packages just as easy as public ones. If you use multiple registries in your organization and need to fetch packages from multiple sources in one single project, you can chain multiple registries and fetch from one single endpoint.

Smart rotating HTTP proxy — load-balance and auto-rotate a pool of upstream HTTP/SOCKS5 proxies with zero-drop connection draining, latency prioritisation, domain pinning, and a built-in management API.

glider is a forward proxy with multiple protocols support, and also a dns/dhcp server with ipset management features(like dnsmasq). We can set up local listeners as proxy servers, and forward requests to internet via forwarders. Act as both proxy client and proxy server(protocol converter). Flexible proxy & protocol chains. Load balancing with the following scheduling algorithm, rr: round robin, ha: high availability, lha: latency based high availability, dh: destination hashing. Rule & priority based forwarder choosing: Config Examples. DNS forwarding server. Force upstream querying by TCP. Association rules between dns and forwarder choosing. Association rules between dns and ipset. dns cache support. Custom dns record. IPSet management (linux kernel version >= 2.6.32). Add ip/cidrs from rule files on startup. Add resolved ips for domains from rule files by dns forwarding server. Serve HTTP and socks5 on the same port. Periodical availability checking for the forwarder.

The python-proxy-headers package provides support for handling custom proxy headers when making HTTPS requests in various python modules. We currently provide extensions to the following packages: urllib3 requests aiohttp httpx None of these modules provide good support for parsing custom response headers from proxy servers. And some of them make it hard to send custom headers to proxy servers. So we at ProxyMesh made these extension modules to support our customers that use Python and want to use custom headers to control our proxy behavior. But these modules can work for handling custom headers with any proxy.

The scrapy-proxy-headers package is designed for adding proxy headers to HTTPS requests in Scrapy. In normal usage, custom headers put in request.headers cannot be read by a proxy when you make a HTTPS request, because the headers are encrypted and passed through the proxy tunnel, along with the rest of the request body. You can read more about this at Proxy Server Requests over HTTPS. Because Scrapy does not have a good way to pass custom headers to a proxy when you make HTTPS requests, we at ProxyMesh made this extension to support our customers that use Scrapy and want to use custom headers to control our proxy behavior. But this extension can work for handling custom headers through any proxy.