Free barracuda proxy software for linux

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.

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.

BlockStop Proxy is a Firefox extension that allows you to view the current page or link using.

Adds a "View this page with BlockStop" or "Open Link Target with BlockStop" option to your Firefox right-click menu, depending on where you click. The BlockStop Proxy extension automatically encodes the target url to maintain anonymity.

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