Free apache 1.3.41 software for linux

apache-top provides real-time display of the active processes from a remote apache server.
With apache-top you can get:
- The active apache processes with their associated PID, the status, the seconds being active, the CPU usage, the asociated VirtualHost, the accessing ip and the request (POST or GET, the file being accessed and the used protocol)
- The server uptime and the last time it was restarted
- The CPU usage
- Requests by second, Kb by second and the average Kb by request
- Number of active and inactive processes
- A graph with the inactive and active processes and their status

Apache MyFaces is the first free open source Java Server Faces implementation.

What is Java Server Faces (JSF)?

Java Server Faces is a new and upcoming web application framework that accomplishes the MVC paradigm. It is comparable to the well-known Struts Framework but has features and concepts that are beyond those of Struts - especially the component orientation.

Look at Suns JSF Page to learn more about the Java Specification Request 127 and to download the specification. You can also find a useful Tutorial there!

Quickstart

Make sure to have a look at our examples - you can find a working distribution here.
Find instructions on installing them yourselves in our Getting Started section. If you cant find information you need on these pages, make sure you also go to our WIKI

Apache Users project is an Apache username enumerator, via /~username requests. This script uses a list of common system names like root, admin etc ...

You should manually check the issue to establish the http return code, ie: 403 as this is needed for the command line. No native SSL support.

USAGE apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)

Sample script:

use IO::Socket;
use Getopt::Std;
getopt ("h: l: p: e: ");
use vars qw( $opt_h $opt_l $opt_p $opt_e );


if ((! $opt_h) || (! $opt_l ) || (! $opt_p ) || (! $opt_e)) {
print "nUSAGE: apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)nn ";

exit 1;
};

$host = $opt_h;
$list = $opt_l;
$port = $opt_p;
$num = $opt_e;

open (LIST, "$list") or die "Unable to open $list ....$!";

&connect;
exit 0;


sub connect {

foreach $name (< LIST >) {


$connection = IO::Socket::INET->new (
Proto => "tcp",
PeerAddr => "$host",
PeerPort => "$port",
) or die "Cant CONNECT to $host on the Port specified.n";

$connection -> autoflush;

chomp $name;
print $connection "GET /~$name HTTP/1.0rnrn";


$results = < $connection >;
if ( $results =~/($num)/g ) {
print "$name exists on $hostn";
};

}

close ($connection);

sleep 1;
};
close LIST;

Apache SNMP Module allows you to monitor different configuration and status values of the Apache Web server using SNMP.
Enhancements:
- Bugfixes, the inclusion of MRTG scripts, and changes to make the module work on the IBM HTTP Server.

Apache::PageKit is a MVCC web framework using mod_perl, XML and HTML::Template.

SYNOPSIS

In httpd.conf

SetHandler perl-script
PerlSetVar PKIT_ROOT /path/to/pagekit/files
PerlSetVar PKIT_SERVER staging

PerlHandler +Apache::PageKit
< Perl>
Apache::PageKit->startup(/path/to/pagekit/files, staging);
< /Perl>
In MyPageKit/Common.pm
package MyPageKit::Common;

use base Apache::PageKit::Model;

sub pkit_dbi_connect {
return DBI->connect("DBI:mysql:db","user","passwd");
}

sub pkit_session_setup {
my $model = shift;
my $dbh = $model->dbh;
return {
session_lock_class => MySQL,
session_store_class => MySQL,
session_args => {
Handle => $dbh,
LockHandle => $dbh,
},
};
}

sub pkit_auth_credential {
my ($model) = @_;

# in this example, login and passwd are the names of the credential fields
my $login = $model->input(login);
my $passwd = $model->input(passwd);

# create a session key
# your code here.........

return $ses_key;
}

sub pkit_auth_session_key {
my ($model, $ses_key) = @_;

# check whether $ses_key is valid, if so return user id in $user_id
# your code here.........

return $ok ? $user_id : undef;
}

Apache::ePerl is a fast emulated Embedded Perl (ePerl) facility.

SYNOPSIS

# Apaches httpd.conf file
# mandatory: activation of Apache::ePerl
PerlModule Apache::ePerl
< Files ~ "/root/of/webmaster/area/.+.iphtml$" >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::ePerl
< /Files >
# optional: configuration of Apache::ePerl
< Perl >
$Apache::ePerl::Config->{BeginDelimiter} = $Apache::ePerl::Config->{EndDelimiter} = !>;
$Apache::ePerl::Config->{CaseDelimiters} = 0;
$Apache::ePerl::Config->{ConvertEntities} = 1;
< /Perl >
# optional: activation of Apache::Status for Apache::ePerl
< Location /perl-status >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::Status
< /Location >

This packages provides a handler function for Apache/mod_perl which can be used to emulate the stand-alone Server-Side-Scripting-Language ePerl (see eperl(3) for more details) in a very fast way. This is not a real 100% replacement for nph-eperl because of reduced functionality under some special cases, principal runtime restrictions and speedup decisions. For instance this variant does not (and cannot) provide the SetUID feature of ePerl nor does it check for allowed filename extensions (speedup!), etc. Instead it uses further features like object caching which ePerl does not use.

But the accepted bristled source file format is exactly the same as with the regular ePerl facility, because Apache::ePerl uses the Parse::ePerl package which provides the original ePerl parser and translator. So, any valid ePerl which works under nph-eperl can also be used under Apache::ePerl.

The intent is to use this special variant of ePerl for scripts which are directly under control of the webmaster. In this situation no real security problems exists for him, because all risk is at his own hands. For the average user you should not use Apache::ePerl. Instead additionally install the regular stand-alone ePerl facility (nph-eperl) for those users.

So, the advantage of Apache::ePerl against the regular nph-eperl is better performance and nothing else. Actually scripts executed under Apache::ePerl are at least twice as fast as under nph-eperl. The reason its not that ePerl itself is faster. The reason is the runtime in-core environment of Apache/mod_perl which does not have any forking overhead.

Apache::Wyrd is a Perl module for HTML embeddable perl objects under mod_perl.

Apache::Wyrd is the core module in a collection of interoperating modules that allow the rapid object-oriented development of web sites in Apaches mod_perl environment (LAMP). This collection includes a very flexible, HTML-friendly method of defining dynamic items on a web page, and interfacing directly to perl objects with them. It comes with many pre-built objects to support a web site such as an authentication module, an reverse-lookup database, granular debugging, and smart forms/inputs and their interfaces to a DBI-compliant SQL application.

The collection is not meant to be a drop-in replacement for PHP, ColdFusion, or other server-side parsed content creation systems, but to provide a more flexible framework for organic custom perl development for an experienced perl programmer who favors an object-oriented approach. It has been designed to simplify the transition from static to dynamic web content by allowing the design of objects that can be operated by a non-perl programmer through the modification of the HTML page on which the content is to be delivered.

The Apache::Wyrd module itself is an abstract class used to create HTML-embeddable perl objects (Wyrds). The embedded objects are interpreted from HTML files by an instance of the abstract class Apache::Wyrd::Handler. Most Wyrds also require an instance of an Apache::Wyrd::DBL object to store connection information and to provide intermediary access to the Apache request and any DBI-style database interfaces.
Each Wyrd has a corresponding perl module which performs work and generates output at the Wyrds location on the HTML page, if any. Each of these objects is a derived class of Apache::Wyrd, and consequently draws on the existing methods of the abstract class as well as implements methods of its own. A few "hook" methods (_setup, _format_output, and _generate_output in particular) are defined in the abstract class for this purpose.

The modules in this distribution are not meant to be used directly. Instead, instances of the objects are created in another namespace (in all POD synopses called BASENAME, but it can be any string acceptable as a single namespace of a perl class) where the Handler object has been configured to use that namespace in interpreting HTML pages (see Apache::Wyrd::Handler).