Free http compression software for linux

Ext2 compression extension (E2compr) is a small patch against the ext2 filesystem that allows on-the-fly compression and decompression. It compresses only regular files; the administrative data (superblock, inodes, directory files etc.) are not compressed (mainly for safety reasons).
Access to compressed blocks is provided for read and write operations. The compression algorithm and cluster size (see section Clusters) is specified on a per-file basis. Directories can also be marked for compression, in which case every newly created file in the directory will be automatically compressed with the same cluster size and the same algorithm that was specified for the directory.
E2compr is not a new filesystem. It is only a patch to the ext2 filesystem made to support the EXT2_COMPR_FL flag. It does not require you to make a new partition, and will continue to read or write existing ext2 filesystems. You should consider it is only a way for the read and write routines to access files that could have been created by a simple utility similar to gzip or compress. Compressed and uncompressed files will coexist nicely on your ext2 partitions.
Usage
Basically, a file is compressed with the command `chattr +c filename, and decompressed with the command `chattr -c filename. You can also do `chattr +c (etc.) on a directory. The directory itself wont be compressed, but any new files created in that directory inherit that directorys compress flag and compression algorithm and cluster size.(1)
Use lsattr to see if a file should be compressed or not, and to see what compression algorithm and cluster size will be used.
Use e2ratio to see how much disk space is used by the compressed form compared to the uncompressed form.
You can also try the `-u or `-r options to lsattr. (The difference is that, for directories, e2ratio finds the disk usage of the whole directory tree, like du, whereas `lsattr -u only shows the space taken by the directory file, like `ls -s.)
Enhancements:
- kernel 2.4.26 and 2.6.18.5 patch sets.
- Allows repeated compress/decompress cycles.
- The ability to compile within a compressed directory tree.
- This release corrects small file sizes and fixes all known GPFs.
- It removes compiler warning messages and regularizes debug output.

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.

The HTTP Time Protocl (HTP) system is a set of utilities to set and maintain the system clock from the HTTP/1.1 (RFC 2616) "Date:" header. HTP requires Libconfig.
The purpose of HTP is provide a simple to use system that can be used on any system that is connected to the internet and can access atleast one web page (either directly or through a proxy) to be able to maintain an accurate clock.
HTTP Time Protocol uses basic statistical analysis to arrive at the most accurate time possible given enough servers. The more servers HTP is configured to use the more accurate the clock can be.
Enhancements:
- Cleanup/simplification of the code.
- A more robust implementation of the "-p" (precision) switch.

HTTP grabber can be used to see what other people on your LAN are downloading as it saves information being sent via the HTTP protocol to disk.

Check the makefile:
if libngrep isnt in /usr/local/lib, change the LFLAGS
if you dont want httpgrabber to be installed in /usr/local/bin, change the directory in the "install" rule.

To install just run "make" and "make install"

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.

HTTP::GetImages is a spider to recover and store images from web pages.

SYNOPSIS

use HTTP::GetImages;

$_ = new HTTP::GetImages (
dir => .,
todo => [http://www.google.com/,],
dont => [http://www.somewhere/ignorethis.html,http://and.this.html],
chat => 1,
);

$_->print_imgs;
$_->print_done;
$_->print_failed;
$_->print_ignored;

my $hash = $_->imgs_as_hash;
foreach (keys %{$hash}){
warn "$_ = ",$hash->{$_},"n";
}

exit;

This module allow syou to automate the searching, recovery and local storage of images from the web, including those linked by anchor (A), mage (IMG) and image map (AREA) elements.

Supply a URI or list of URIs to process, and HTTP::GetImages will recurse over every link it finds, searching for images.

By supplying a list of URIs, you can restrict the search to certain webservers and directories, or exclude it from certain webservers and directories.

You can also decide to reject images that are too small or too large.

HTTP::Async is a Perl module that can process multiple HTTP requests in parallel without blocking.

SYNOPSIS

Create an object and add some requests to it:
use HTTP::Async;
my $async = HTTP::Async->new;

# create some requests and add them to the queue.
$async->add( HTTP::Request->new( GET => http://www.perl.org/ ) );
$async->add( HTTP::Request->new( GET => http://www.ecclestoad.co.uk/ ) );
and then EITHER process the responses as they come back:
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
OR do something else if there is no response ready:
while ( $async->not_empty ) {
if ( my $response = $async->next_response ) {
# deal with $response
} else {
# do something else
{
}
OR just use the async object to fetch stuff in the background and deal with the responses at the end.
# Do some long code...
for ( 1 .. 100 ) {
some_function();
$async->poke; # lets it check for incoming data.
}

while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}

Although using the conventional LWP::UserAgent is fast and easy it does have some drawbacks - the code execution blocks until the request has been completed and it is only possible to process one request at a time. HTTP::Async attempts to address these limitations.

It gives you a Async object that you can add requests to, and then get the requests off as they finish. The actual sending and receiving of the requests is abstracted. As soon as you add a request it is transmitted, if there are too many requests in progress at the moment they are queued. There is no concept of starting or stopping - it runs continuously.

Whilst it is waiting to receive data it returns control to the code that called it meaning that you can carry out processing whilst fetching data from the network. All without forking or threading - it is actually done using select lists.

The NoMachine NX Web Companion is a small Java applet and a plugin interface that links the availability of the Web to the unmatched power of NX.

NoMachine NX is a fast terminal server system based on the X11 protocol. In addition, NX also translates and embeds the MS Windows Terminal Server and VNC protocols into X/NX. NX is an order of magnitude faster than VNC or X11 and can run on bandwidth as narrow as 10 kBit/sec.

By embedding RDP and RFB, it enables users to compress and accelerate remote Windows and VNC sessions. NX lets you work fluently even across slow links like modems.

The NX project provides a suite of libraries and X11 proxying agents implementing efficient compression and optimized transport of X11, SMB, IPP, HTTP, and arbitrary protocols like audio over the Internet.