Free http getimages software for linux

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"

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::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.

HTTP::Server::Simple::Mason is an abstract baseclass for a standalone mason server.

SYNOPSIS

my $server = MyApp::Server->new();

$server->run;

package MyApp::Server;
use base qw/HTTP::Server::Simple::Mason/;

sub mason_config {
return ( comp_root => /tmp/mason-pages );
}

INTERFACE

See HTTP::Server::Simple and the documentation below.

mason_handler

Returns the servers HTML::Mason::CGIHandler object. The first time this method is called, it creates a new handler by calling new_handler.

handle_request CGI

Called with a CGI object. Invokes mason and runs the request

handle_error ERROR

If the call to handle_request dies, handle_error is called with the exception (that is, $@). By default, it does nothing; it can be overriden by your subclass.

new_handler

Creates and returns a new HTML::Mason::CGIHandler, with configuration specified by the default_mason_config and mason_config methods. You dont need to call this method yourself; mason_handler will automatically call it the first time it is called.

handler_class

Returns the name of the Mason handler class invoked in new_handler. Defaults to HTML::Mason::CGIHandler, but in your subclass you may wish to change it to a subclass of HTML::Mason::CGIHandler.

setup_escapes $handler

Sets up the Mason escapes for the handler $handler. For example, the h in

< % $name | h % >

By default, sets h to HTTP::Server::Simple::Mason::escape_utf8 and u to HTTP::Server::Simple::Mason::escape_uri, but you can override this in your subclass.
mason_config

Returns a subclass-defined mason handler configuration; you almost certainly want to override it and specify at least comp_root.

default_mason_config

Returns the default mason handler configuration (which can be overridden by entries in mason_config).

escape_utf8 SCALARREF

does a css-busting but minimalist escaping of whatever html youre passing in.

escape_uri SCALARREF

Escapes URI component according to RFC2396

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.

HTTP::WebTest::XMLParser is a Perl module to parse webscript in XML representation.

SYNOPSIS

use HTTP::WebTest::XMLParser;
my ($tests, $opts) = HTTP::WebTest::XMLParser->parse($xmldata);

use HTTP::WebTest;
my $wt = new HTTP::WebTest;
$wt->run_tests($tests, $opts);

HTTP::WebTest::XMLParser->as_xml($tests, $opts, { nocode => 1 });

Parses a wtscript file in XML format and converts it to a set of test objects.

XML SYNTAX

The xml format follows wtscript closely, with the following rules:

- the root element is
- global paramters are in a element
- test definitions are in elements
- a list is represented by a element
- a scalar param. is represented by a element
- a code segment is represented by a element
- named parameters are named throug a name attribute

The DTD is available in scripts/webtest.dtd from the distribition. For examples see the test definitions in t/*xml from the distribution.

A conversion script from wtscript to XML is available in scripts/testconversion from the distribution. This script also converts XML definitions from earlier alpha versions of this module.