Free http proxy software for linux

HTTP Proxy Client is the small set of libraries and scripts, which provides transparent access to Internet via HTTP proxy for programs, which uses TCP/IP for communication.
The list of programs includes: telnet, ftp, licq, cvs, smth else? Project implements dynamic library, that can be preloaded before program run.
The library substitutes some system calls (connect(), gethostbyaddr(), gethostbyname()), with calls, which makes TCP/IP connection through HTTP proxy. This allows client programs behind HTTP proxy work with Internet without limitations.
At the moment tested on i386 Linux, i386/sparc Solaris.
Enhancements:
- While using dotted address, applications will attempt to connect regardless DNS lookup result.

Spike Proxy is an open source HTTP proxy for finding security flaws in web sites.

SPIKE Proxy is part of the Spike Application Testing Suite and supports automated SQL injection detection, web site crawling, login form brute forcing, overflow detection, and directory traversal detection.

To Use:

python spkproxy.py [ optional port argument, 8080 is default ]
Then set up your browser to use that port for both HTTP and
HTTPS proxies.

Then watch the traffic go!

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.

httptype is a program that returns the http host software of a website. It is written in Perl.
httptype reads a list of http hosts and optionally the port number for each of these. It queries each host, displaying the type of HTTP server running on that host. It reads the http_proxy and no_proxy environment variables to determine whether to use a proxy or not.
httptype reads a list of http servers and, optionally, the port number for each of these. It then queries each of the hosts and displays the HTTP server software of the host.
Input may be read from a host file if specified using the --hosts switch:
httptype --hosts [hostfile]
If hostfile is omitted or `-, httptype reads from standard input. See Format of host file for more info.
A single host may be queried by passing its name on the command line:
httptype host [port]
If port is omitted, 80 is used.
If no host file is specified through the --hosts file and no host is specified on the command line, httptype will read the list from standard input. See Format of host file for more info.
httptype will read the http_proxy environment variable and try to determine if a proxy server is being used. This setting may be overridden using the --proxy switch:
httptype --proxy proxyhost[:proxyport]
If proxyport is omitted, 80 is used.
If the proxy server is `none, no proxy is used. This is typically used to prevent httptype from using the proxy server specified by http_proxy. The --noproxy switch can be used to achieve the same.
Additionally, you may use the no_proxy environment variable to specify a comma delimited list of hosts for which httptype should not use the proxy. If httptype comes across any of these hosts, it will make a direct connection to them.
Enhancements:
- made 1.3.8 stable and renamed to 1.2.3

FSP Proxy provides a proxy server for FSP to HTTP protocol translation.
FSP Proxy is a proxy server for FSP to HTTP/1.0 protocol translation. It also accepts gopher:// URLs as an alias for fsp://. You can set it up as a gopher proxy in your browser, and easily access FSP sites.
This proxy supports HTTP/1.1 on output side and FSP v2 on input side. Subrange byte requests are supported, resume works nicely. Simply FSP v2 over HTTP/1.1. This proxy do not caches anything.
This proxy makes playing with FSP very easy for newcommers, there is no need to learn classic fsp command line interface tools. Everybody who can handle downloads in browser, can now play with FSP sites available through Internet.
Enhancements:
- use getopt from stdio.h instead of getopt.h in fspscan.c
- fspscan now compiles on AIX and other OS without glibc (hoaxter)
- !! fixed fatal bug from b23. Server sends large packets to clients if
- client request has not prefered reply size inside. This confuses
- all old fsp clients.
- common/strdup.c removed
- bsd_src/function.c bcopy -> memmove
- removed STDC_HEADER checks, drop support for pre-ANSI compilers
- started work on alternate SCons based build system
- fspd: use urandom, not random -> avoid hangs on Lin suck 2.6
- build system converted to SCons
- !! fixed directory listing bug in client library introduced in beta23
- improvements to security of FSP clients
- seq. numbers are now randomized
- seed random number generator in fsp clients
- check cmd in received packets
- check pos in received packets

Shrew Proxy/Filter is a tiny proxy built on WEBricks HTTPProxyServer, extended for both URL and content filtering. Shrew Proxy/Filter is designed to be small, simple to configure, and easy to install.

It is extremely small, lightweight, and works quite well. All blacklists (both URL and content) are plain text, so most published lists can be simply dropped in and used.

HTTPTunnel is a simple client/server application for creating an HTTP tunnel between two machines, optionally via a Web proxy.
This is a small application for tunnelling an arbitrary TCP socket connection over HTTP. It can be used, for example, to tunnel traffic out from behind a restrictive firewall that only allows outgoing HTTP web connections.
The basic idea is that you run an instance of the HTTP Tunnel application locally in client mode, that then connects out to another instance that you run at the remote end of the tunnel in server mode.
You then connect to the local client end of the tunnel with the application whose traffic you wish to tunnel, and all communications are then wrapped in HTTP. The tunnel may also go via a HTTP proxy, either explicitly or transparently.
Enhancements:
- This release includes some major bugfixes and improvements in the tunneling error detection and retransmission code.
- It also introduces support for building and running under Cygwin.