Free https web proxy software for linux

HAVP (HTTP Antivirus Proxy) is a proxy with a ClamAV anti-virus scanner. HTTP Anti Virus Proxy aims are continuous, non-blocking downloads and smooth scanning of dynamic and password protected HTTP traffic.
Havp antivirus proxy has a parent and transparent proxy mode. It can be used with squid or standalone.
Main features:
- HTTP Antivirus proxy
- Scans complete incomming traffic
- Nonblocking downloads
- Smooth scanning of dynamic and password protected traffic
- Can used with squid or other proxy
- Parent proxy support
- Transparent proxy support
- Logfile
- Process change to defined user and group
- Daemon
- Use Clamav (GPL antivirus)
- Operating System: Linux
- Written in C++
- Released under GPL
Enhancements:
- Experimental support was added for chunked Transfer-Encoding, which fixes some broken sites.
- The IGNOREVIRUS configuration directive was added for whitelisting virus names.
- The CLAMBLOCKBROKEN configuration directive was added.
- Detection with AVG was improved.
- HAVP is killed if database reloading fails for Library Scanner.
- The URL is logged when a crashed scanner process is detected.
- The build system updated, adding the --prefix, --sbindir, --sysconfdir, and --localstatedir options.

phpWebPROXY provides a simple Web proxy written in PHP.

It allows you to run your Web surfing through your own Web server and bypass filters which may be between you and what you want to see.

It supports cookies, and its Web-based location bar lets you move around the Web easily.

IMAP Calendar Proxy implements an HTTP proxy that converts HTTP PUT requests of vcalendar data to separate messages stored on an IMAP server.

IMAP Calendar Proxy project can be used with Mozilla Sunbird/Calendar to allow storage of a calendar via IMAP.

There are many issues with the program in its current state. Consider it alpha quality, and you may lose calendar data if you use it. Its more of a proof of concept right now. Its rather slow if you have a large calendar.

Ideally IMAP support should be built into Mozilla. This is just a hack. Id like to hear any feedback on how it works. See the TODO file for features Id like to implement.

Sunbird can post calendars to a remote HTTP server via HTTP PUT and to
synchronize via a GET before a PUT. This proxy should run on the same system
you run Sunbird on. It makes a connection to an IMAP server and selects
a specified folder.

It then retrieves all calendar data from that server and caches it it memory. Any changed to the calendar are HTTP PUT to this proxy, and it determines what to do on the IMAP server (delete, change, add). Instead of posting the whole calendar back to the server, it only posts the differences.

If you run the proxy elsewhere on the network, you will not get any bandwidth
savings because the HTTP PUT and GET are still done over the network.

IMAP Proxy server is a caching IMAP proxy server. It was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction.

This behaviour can cause tragic performance problems on the IMAP server. imapproxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs out.

When the webmail client connects again, imapproxy will determine if theres a cached connection available and reuse it if possible.

How does imapproxy keep track of which server connection is for which user?

Upon the first successful login to the real IMAP server (through the proxy), imapproxy fills in a little record that contains the username, an md5 digital signature of the password and the server socket descriptor thats being used.

After you log out and then log back in again, imapproxy just has to find a record that matches your username and password. These records are stored in a hash table (with the username being the hash key) in memory, so the lookups are pretty fast.

Can IMAP Proxy support multiple backend servers?

If you want IMAP Proxy to be able to proxy to multiple backend IMAP servers, you can run multiple instances of IMAP Proxy and make sure each instance is looking at a different configuration file.

Before you do this, take a look at perdition which appears to have been designed with this specific task in mind.

SSL Proxy server listens on a TCP port, accepts SSL connections, and forwards them to another local or remote TCP port.
For example, it is possible to create an HTTPS server if you have an HTTP server and you run an SSL Proxy server on port 443 which forwards the connections to port 80.
SSL Proxys design makes it as secure as possible and still perform well.
Enhancements:
- Improved certificate handling (chained certificates are now supported), more error information on SSL protocol errors during SSL_accept(), -U and -D options (buffer size), and a "powered by" logo.

Japt-Proxy is a JAVA based Caching Proxy for Debians APT-System. Japt-Proxy is very reliable and lightning fast. Japt-Proxy is usually used in environments where several Debian systems have to be kept up-to-date without downloading the same files over and over again from the debian mirrors. Mostly these environments are data centers, Linux-powered companies, schools, public authorities and so on.
Often Japt-Proxy is used because of small sized internet connections but it is also useful to install complete debian systems over the net (read: over the proxy). Even with high volume internet connections Japt-Proxy can dramatically reduce the time to install or update Debian on many machines.
Why Java?
I know there are people out there thinking "Hey? Why Java?". There are a bunch of reasons why people asking those questions. I have a simple answer to all those questions. The answer is, that Java enabled me to easily develop the fastest and most reliable APT-Proxy. Java and the Apache Software Foundation provides such good libraries for this job, that it wasnt very hard to bring up this tool.
If you dont trust, test it - the installation takes less than five minutes!
Doesnt a general proxy server supersede an APT-Proxy?
No, it doesnt. Japt-Proxy knows the characteristics of a Debian archive and their files. It knows, for example, that .deb files wont change, because newer files would have a new name (the version is always part of the filename), hence it wont recheck if there is a newer version of this specific file.
Furthermore you can configure the Japt-Proxy to delete old versions of a package in its cache directory - a general proxy cache would simple delete files that havent been requested for some time.
So, a general caching proxy like Squid is a perfect tool for caching "normal" internet traffic. If you need a proxy for faster APT access - Japt-Proxy is the right tool for you.
Main features:
- Caching of all apt requests from Debian archives
- Multi-threaded architecture which increases the download speed enormously when several machines are requesting packages
- Builds up a partial mirror directory automatically, with exactly the same directory structure and filenames as the original mirror
- Automatic and configurable cache cleanup (purging packages in cache if newer versions exists)
- Makes sources.list configuration easier for multiple machines - if you change your internet backend server you only have to make the change once in Japt-Proxy, instead of on all Debian machines
- Works with multiple architectures
- Backend support for HTTP and FTP
- existing .debs can be copied into the Japt-Proxy cache directory (from a CD or DVD for example) and will be used by the Proxy automatically

tinyproxy is a lightweight HTTP proxy licensed under the GPL. Designed from the ground up to be fast and yet small, it is an ideal solution for sites where a full-featured HTTP proxy is required, but the system resources required to run a more demanding HTTP proxy are unavailable. tinyproxy is fully compatible with all existing web browsers.
Main features:
Anonymous mode
- Allows you to specify which HTTP headers should be allowed through, and which should be blocked - this allows you to restrict both what data comes to your web browser from the HTTP server (eg, cookies), and to restrict what data is allowed through from your web browser to the HTTP server (eg, version information).
Easily modified
- If youre looking to build a custom web proxy, tinyproxy is very easy to modify to your custom needs - the source is straightforward, adhering to the KISS principle. As such, it can be used as a foundation for anything you may need a web proxy to do (send patches!)
Remote monitoring
- Using the remote monitoring feature, you can access proxy statistics from afar, letting you know exactly how busy the proxy is.
Load average monitoring
- tinyproxy can be configured to watch the load average on most platforms, and start refusing requests when the load reaches a certain point - you may recognize this feature from sendmail.
Access control
- You can configure tinyproxy to only allow requests from a certain subnet, or from a certain interface, thus allowing you to ensure that random, unauthorized people will not be using your proxy.
Secure
- With a bit of configuration (specifically, making the log file owned by nobody and running it on a port >1024), tinyproxy can be made to run without any special privileges, thus minimizing the chance of system compromise. Furthermore, it was designed with an eye towards preventing buffer overflows. The simplicity of the code ensures it remains easy to spot such bugs.
Small footprint
- As mentioned above, tinyproxy requires very little in the way of system resources - the memory footprint tends to be around 2MB with glibc, and the CPU load increases linearly with the number of simultaneous connections (depending on the speed of the connection). Thus, tinyproxy can be run on a spare, older machine, or even a workstation, without any noticeable impact on performance.