Free http requests software for linux

HttpAuth is a daemon and framework for authenticating HTTP requests. It supports Basic and Digest authentication against various databases such as LDAP, PostgreSQL, or MySQL.
HttpAuth project also supports NTLM authentication against a Windows Server.
Compatibility: Various web servers can talk with httpauthd. Currently modules, plugins or code for the following systems have been written:
- Apache 1.3.x
- Apache 2.x
- Java Servlets
- Jetty Web Server
Enhancements:
- A crash which occurred when doing some sort of Basic authentication was fixed.
- Numbers are now allowed in handler names.
- The program reconnects properly to httpauthd when that daemon has been restarted.
- The Java (Jetty) authenticator now supports NTLM properly.
- A bug where Apache 2.x wouldnt lock down credentials for NTLM properly to a single connection was fixed.

lns.http is a simple framework for writing Common Lisp web applications. The project handles the incoming connections, parses HTTP headers and queries, and finally hands control over to your URL handler.

lns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.

The lns.http web server uses lisp-network-server to take care of network handling.

This software is licensed unter the LGPL.

HTTP extension for PHP allows building absolute URIs, RFC-compliant HTTP redirects, RFC-compliant HTTP date handling, parsing of HTTP headers and messages, caching by "Last-Modified" and/or ETag (with an on the fly option for ETag generation from buffered output), sending data/files/streams with (multiple) ranges, negotiating user-preferred language/charset, and convenient request functionality built upon libcurl.
PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, and HttpMessage.
Main features:
- Building absolute URIs
- RFC compliant HTTP redirects
- RFC compliant HTTP date handling
- Parsing of HTTP headers and messages
- Caching by "Last-Modified" and/or ETag (with on the fly option for ETag generation from buffered output)
- Sending data/files/streams with (multiple) ranges support
- Negotiating user preferred language/charset
- Convenient request functionality built upon libcurl
- PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, HttpMessage.
Enhancements:
- This release fixes bug #11359: HttpMessage::toMessageTypeObject() does not populate POST fields.

libjhttpd project is a simple HTTP/1.0 compliant, threaded webserver-library written in Java.
Main features:
- threaded
- very fast
- supports MIME-Types
- flexible configuration
- supports binary multipart POST-Requests, i.e. File Uploads

HTTP::Browscap is a Perl module that can parse and search browscap.ini files.

SYNOPSIS

use HTTP::Browscap;

my $capable = browscap();

if( $capable->{wap} ) {
output_WAP();
}

if( $capable->{css} > 1 ) {
# Browser can handle CSS2
}

# OO interface
my $BC = HTTP::Browscap->new( browscap.ini );

$capable = $BC->match( $ENV{HTTP_USER_AGENT} );

ABSTRACT

Browscap.ini is a file, introduced with Microsofts IIS, that lists the User-Agent strings that different browsers send, and various capabilities of those browsers. This module parses browscap.ini and allows you to find the capability definitions for a given browser.

Starting with Microsofts IIS, a browscap.ini file was used to list the capabilities of various browsers. Using the User-Agent string that a browser sends in the HTTP request, the capabilities of a browser are retrieved. If an exact match of the User-Agent string isnt found, wild-card expantion is done. If all fails, a default browser definition is used.

There are limits the usefulness of browscap.ini. It only detects if a browser has a certain capability, but not if this capability has been deactivated or if its a buggy implementation. In particular, most CSS and JavaScript implementations will make you scream.

HTTunnel::Client is a client class for Apache::HTTunnel.

SYNOPSIS

my $hc = new HTTunnel::Client("http://localhost/httunnel") ;
$hc->connect(tcp, $some_host, $some_port) ;

$hc->print(some request) ;
my $some_response = $hc->read(1024) ;

$ch->close() ;

HTTunnel::Client is the client class to Apache::HTTunnel. It allows the creation of a network connection tunnelled through HTTP. All data sent and received during this connection will be transported inside normal HTTP requests.

HTTunnel::Client extends LWP::UserAgent, so all LWP::UserAgent methods are available through HTTunnel::Client.

CONSTRUCTORS

new ( URL, [ARGS] )

Creates an HTTunnel::Client object that will use URL to contact the Apache::HTTunnel server. ARGS are is passed directly to the LWP::UserAgent constructor.

METHODS

connect ( PROTO, HOST, PORT, [TIMEOUT] )

Asks the Apache::HTTunnel server to establish a connection of protocol PROTO to HOST:PORT. An exception is thrown if an error occurs.

Accepted values for PROTO are tcp and udp.

print ( DATA )

Asks the Apache::HTTunnel server to write DATA to the established remote connection. An exception is thrown if an error occurs.
DATA can be a scalar or a list, in which case the list items are concatenated together.

read ( LEN, [TIMEOUT], [LIFELINE], [LIFELINE_CUT_ACTION] )

Asks the Apache::HTTunnel server to read up to LEN bytes from the established remote connection. An exception is thrown if an error occurs.

When trying to read, HTTunnel::Client will establish an HTTP connection to the Apache::HTTunnel server asking that LEN bytes be read. If no data is available after TIMEOUT seconds (the default value is 15 seconds), the HTTP connection is closed by the server and the read method will establish a new one. This will go on until some data or EOF is returned.

Therefore read will return only when some (or no more) data is available to be read (like the regular read).

LIFELINE can be any valid filehandle from which one can read. If used, read will interrupt its connection loop and execute LIFELINE_CUT_ACTION when data (or EOF) is available to be read from LIFELINE. It will then return undef.
LIFELINE_CUT_ACTION wust be a CODE ref. The default value is

sub {die("lifeline cutn")}

These features can be used if you want fork and to start a process that does nothing but reads and returns the data via a pipe. You can then use a second pipe to make sure the reader process terminates when the master process terminates.

Here is an example:

my $lifeline = new IO::Pipe() ;
my $reader = new IO::Pipe() ;
my $pid = fork() ;
if ($pid){
$reader->reader() ;
$lifeline->writer() ;

# Read data from $reader...
}
else {
$reader->writer() ;
$reader->autoflush(1) ;
$lifeline->reader() ;

while (1){
my $data = $hc->read(1024, 15, $lifeline, sub {exit()}) ;
exit() unless defined($data) ;
print $reader $data ;
}
}
close ( )

Asks the Apache::HTTunnel server to close a previously established connection.
get_peer_info ( )

The get_peer_info method returns information about the remote connection. A string containing the IP address and port number, separated by a colon (:) is returned. This method can be useful with UDP connections to validate the sender of each packet.

request_callback ( REQUEST )

The request_callback method is a callback method that can be used to access the HTTP::Request object just before it is sent. The default implementation does nothing.

response_callback ( RESPONSE )

The response_callback method is a callback method that can be used to access the HTTP::Response object just after it is received. The default implementation does nothing.

HTTP-FUSE-KNOPPIX is a "pile-up" KNOPPIX linux distribution. HTTP-FUSE KNOPPIX downloads pieces of Root Filesystem from a HTTP server when the piece is requested, although normal KNOPPIX requires whole 700MB ISO image at first. The piece is "piled up" on your PC.

The first minimum parts of HTTP-FUSE-KNOPPIX are bootloader with "Linux kernel" and "miniroot". The size is only 6MB. The rest of parts "ROOT file system" which size is 700MB is downloaded on demand as a small piece of block device.

The original block device which includes ROOT file system is split into small data-piece. Each small data-piece is compressed and saved to a file. The files are called "split-and-compressed block files". Split-and-compressed block files is downloaded when it is required. Split-and-compressed block files compose a virtual block device with HTTP-FUSE.

HTTP-FUSE-KNOPPIX selects ROOT file system at boot time. It means HTTP-FUSE-KNOPPIX doesnt make a CD-ROM for customization. It just upload the customized Root File system on HTTP server.

Furthermore the uploaded "split-and-compressed block files" for customized KNOPPIX are difference only. The most split-and-compressed blocks files are shared between original KNOPPIX and customized KNOPPIX. The feature makes small volume of a server when customized KNOPPIX is added.