Free what is a proxy server software for linux

Whois Proxy provides a CGI or command line whois proxy tool.

Whois Proxy is a Perl whois tool for looking up the owners, technical contacts, abuse desk, IP address, NIC handle, or ASN of any domain on the internet.

A complete rewrite of the GeekTools whois proxy, it also runs either as a Web application or on the command line but has a few more features.

The Web interface is validated strict XHTML and CSS2.

NTLM Authorization Proxy Server is a proxy software that allows you to authenticate via an MS Proxy Server using the proprietary NTLM protocol.
Since version 0.9.5 APS has an ability to behave as a standalone proxy server and authenticate http clients at web servers using NTLM method.
It can change arbitrary values in your clients request header so that those requests will look like they were created by MS IE. It is written in Python v1.5.2 language.
Main features:
- supports NTLM authentication via parent proxy server (Error 407 Proxy Authentication Required);
- supports NTLM authentication at web servers (Error 401 Access Denied/Unauthorized);
- supports translation of NTLM scheme to standard "Basic" authentication scheme;
- supports the HTTPS CONNECT method for transparent tunnelling through parent proxy server;
- has ability to change arbitrary values in clients request headers;
- supports unlimited number of client connections;
- supports connections from external hosts;
- supports HTTP 1.1 persistent connections;
- stores users credentials in config file or requests password from a console during the start time;
- supports intelligent failure detection and failover between multiple upstream proxies;
Enhancements:
- This release fixes a minor bug with Python 1.5.2 compatibility.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

Proxy Detector is a PHP class that can detect HTTP requests via proxy. This class can detect if a visitor uses a proxy server by scanning the headers returned by the user client.
When the user uses a proxy server, most of the proxy servers alter the header. The header is returned to PHP in the array $_SERVER.
Enhancements:
- This is the first release of the class and implementation example.

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

SPYCE is a server-side language that supports simple and efficient Python-based dynamic HTML generation, otherwise called Python Server Pages (PSP).

Those who are familiar with JSP, PHP, or ASP and like Python, should have a look at Spyce. Its modular design makes it very flexible and extensible. Spyce - Python Server Pages can also be used as a command-line utility for static text pre-processing or as a web-server proxy.

The supported adapters are:

* Fast CGI:The default Spyce integration with Apache is acheived via FastCGI, a CGI-like interface that is relatively fast, because it does not incur the large process startup overhead on each request.

* mod_python: If you really must have the fastest Spyce implementation (see the performance numbers), it is currently through an Apache module called mod_python. Spyce has been tested with mod_python version 2.7.6 (and version 3.0.3 with apache 2.0.37). You can try to find some mod_python rpms here, but in general one must compile mod_python from sources. The reason for this is because mod_python links with the Python library it finds on your system at compile time. Thus, even if you have the correct Python version installed on your system, mod_python will be using the Python library version on the system where it was compiled. Also, note that mod_python (or rather Apache) needs a Python that has been compiled without threading, so you may need to recompile Python as well for this reason. The process is not very difficult (just the usual: ./configure; make; make install dance), but hopefully someone will suggest a better route in time. In any case, make sure you can first get mod_python running on your system, if that is that is your chosen Apache integration route.

* Web server: Another fast alternative is to serve Spyce files via a proxy. This involves running Spyce in web-server mode, and configuring the main web server to forward the appropriate requests. The built-in Spyce web server can also be used to serve requests directly, but this is highly discouraged for production environments.

* CGI: Failing these alternatives you can always process requests via regular CGI, but this alternative is the slowest option and is intended primarily for those who do not have much control over their web environments.

* Command line: Lastly, one can use Spyce as a command-line tool for pre-processing Spyce pages and creating static HTML files.

YAZ Proxy application is highly configurable and can be used in a number of different applications, ranging from debugging Z39.50-based applications and protecting overworked servers, to improving the performance of stateless WWW/Z39.50 gateways.
Main features:
- Configurable logging
- SRU/SRW server function, to allow any Z39.50 server to also support the ZiNG protocols
- Load balancing across multiple backend servers
- Session-sharing and pre-initialization to improve performance in servers with expensive session initialization
- Configurable request filtering, to keep bad requests from reaching the server
- XML support -- MARC records can be converted to MARCXML, and XSLT-transformations allow the proxy to support arbitrary retrieval schemas in XML
- Load governor function limits requests from aggressive batch-mode clients
- Efficient multiplexing software enables small memory footprint and very high performance
NOTE: The YAZ Proxy, a complete application, is available under the GPL license. Other licensing terms are available to commercial vendors upon request.