Free https proxy software for linux

YACY is a distributed Web crawler and also a caching HTTP/HTTPS proxy. Pages that pass through the proxy are indexed and can be searched using a built-in HTTP server.
YACY peers connect each other and form a P2P-based index exchange network based on distributed hash tables. Explicit web crawls can be done locally or collaboratively, forming a global search and distributed indexing engine for the Web.
YACY also provides URL filtering with blacklist sharing among other proxy peers, individual Web and servlet page hosting, a file sharing zone, and a database engine.
Main features:
- Search your own or the global index
- Crawl your own pages or start distributed crawling
- Run your peer to support other YaCy crawlers
- Provide Information on your peer using the built-in http-server, file-sharing zone and wiki
- Built-in caching http proxy
- Indexing benefits from the proxy cache; private information is not stored or indexed
- Usage of the proxy is not a requisite for web indexing, but it enables you to access the new top-level-domains .yacy
- Filter unwanted content like ad- or spyware; share your web-blacklist with other peers
- Easy installation! No additional database required!
- No central server!
- GPLed, freeware
Enhancements:
- An auto-updater and support for multiple search networks have been added, and the option to index intranet sites in separated networks has been enabled.
- Some interface functions have also been enhanced.

Mobile Web Proxy is a (CGI) tool to make more Web pages available from some mobile devices (cell phone Web browsers, etc.).
When I began using my cell phones mobile web browser, one of the things I realized was that there were a lot of web pages that my cell phones web browser simply wouldnt let me see. My shiny new Motorola Razr from T-Mobile, for many pages, would display an error message like "413: Page cannot be displayed." It happened annoyingly often; browsing the web from my cell phone was a lot like trying to read a book or a magazine with large chunks simply ripped out. And when I tried troubleshooting, I might have missed something, but it seemed like a big problem without an easily available solution.
So I tried to provide my own solution. I made a proxy that would present webpages for the mobile web so that they would display in a way that would work for my cell phones web browser. Technologies include paging, tag cleaning, and optional caching to improve performance, but without getting into technical details, this means that I can access some pages on the web that I couldnt access earlier.
Enhancements:
- A bug that caused the script to spuriously report 404 errors was fixed.
- A smaller default page size was set so that tag-rich pages would be rendered in a way more likely to be displayable on mobile Web browsers.

Apache::ProxyConf is a Perl module that can generate proxy configuration for browsers.

SYNOPSIS

# In httpd.conf:

< Location / >
SetHandler perl-script
PerlHandler Apache::ProxyConf
PerlSetVar ProxyConfConfig "/some/location/proxyconf.ini"
< /Location >

The Apache::ProxyConf is used to configure the proxy settings in browsers automatically. The modules returns a script that conforms to the Navigator Proxy Auto-Config File Format. The module is suitable for large scale installations that have multiple (cascading) proxies. It can be used to return the closest proxy based on the network topology. Failover and load distribution is also provided.

Browser configuration

The (virtual) webserver must be entered in the Autoconfigure URL of the browser to make use of the ProxyConf script.

http://proxyconf.some.domain/

In IE the URL must be specified in the Address field, just below the Use automatic configuration script tickbox.

THE CONFIGURATION FILE

The ProxyConf module first reads a .ini-style configuration file to determine the proxy settings of the network. The configuration file contains three sections: proxy, noproxy and https.

The proxy section

The sections proxy and https have an identical format. They contain lines of the form subnet=proxyip:port.

Single proxy

[proxy]
172.16.32.0/20=172.16.32.10:3128

The subnet 172.16.32.0/20 has a single proxy defined. The proxy server is 172.16.32.10 and it listens on port 3128.

Multiple proxies

[proxy]
172.16.0.0/20=172.16.0.10:3128,172.16.0.20:3128

Multiple proxy servers are defined in a comma separated list. In this example clients in the 172.16.0.0/20 subnet use 172.16.0.10 as their primary proxy server. When this server becomes unavailable, the clients will move over to 172.16.0.20 for their proxy requests.

Multiple proxies with load distribution

[proxy]
172.16.0.0/20=(172.16.0.10:3128,172.16.0.20:3128)

When proxy servers are placed between brackets, the load is distribution amongst the proxies. Some clients will have the first proxy as primary and some clients will have the second proxy as primary. The other proxy is used as a backup. The order in which the proxies are tried depends on the IP address of the client. The script is deterministic, so for a given IP address the priority list is always the same.

To determine the proxy list for a given IP address multiple rules may be applied. Subnets are tried from the highest to the lowest mask. The module puts all proxies that are found in a list.

The noproxy section

The noproxy section contains hosts that should be contacted by the clients directly. Noticeably, web servers that use NTLM authentication will not work when clients connect to them via a proxy server. The syntax for specifying noproxy hosts is subnet=fqhn1,fqhn2,... Alternatively, the multiline syntax can be used, as shown in this example.

[noproxy]
0.0.0.0/0=<<less