Free http webtest software for linux

HTTP::WebTest is a Perl module for testing static and dynamic web content.

SYNOPSIS

use HTTP::WebTest;

my $webtest = new HTTP::WebTest;

# run test from file
$webtest->run_wtscript(script.wt);

# or (to pass test parameters as method arguments)
$webtest->run_tests($tests);

Introduction

This module runs tests on remote URLs containing Perl/JSP/HTML/JavaScript/etc. and generates a detailed test report. This module can be used "as-is" or its functionality can be extended using plugins. Plugins can define test types and provide additional report capabilities. This module comes with a set of default plugins but can be easily extended with third party plugins.

The wt script is provided for running HTTP::WebTest from the command line.
The test specifications can be read from a parameter file in wtscript format or input as method arguments. The test results can be displayed on the terminal, directed to a file, stored in a scalar variable. The test results can also be emailed. The report can be modified and extended using report plugins.

Each URL/web file is tested by fetching it from the web server using a local instance of an HTTP user agent. The basic test is simply whether or not the fetch was successful. You may also test using literal strings or regular expressions that are either required to exist or forbidden to exist in the fetched page. You may also specify tests for the minimum and maximum number of bytes in the returned page. You may also specify tests for the minimum and maximum web server response time.

Data flow for HTTP::WebTest:

-------------- -------------
| | | |
| Input |------------->| WebTest |
| parameters | | |
| | -------------
-------------- | ^
| |
V |
------------- ------------
| | request | |
| Remote || user |
| | response | agent |
------------- | |
------------

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"

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.

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.

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

darkhttpd 1.7 is yet another great addition to your computer. It is actually a secure, lightweight, fast, single-threaded HTTP/1.1 server for static content.

Enhancements:

• Links in directory listings which contain special characters are now URL encoded.

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.