Free apache 2 software for linux

mod_auth_pam is an authentication module for the Apache Web-Server.

The PAM authentication module implements Basic authentication on top of the Pluggable Authentication Module library.

Thereby it supports standard unix passwd, shadow, NIS, SMB auth and radius (-> complete list of modules) authentication transparently and easily interchangeable, wherever the HTTP protocol allows it.

Apache Solr is a high performace search server based on Lucene, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, and a Web administration interface.
The project is currently under incubation at the Apache Software Foundation.
Instructions for Building Apache Solr
1. Download the J2SE 5.0 JDK (Java Development Kit) or later from http://java.sun.com. You will need the JDK installed, and the %JAVA_HOME%bin directory included on your command path. To test this, issue a "java -version" command from your shell and verify that the Java version is 5.0 or later.
2. Download the Apache Ant binary distribution from http://ant.apache.org. You will need Ant installed and the %ANT_HOME%bin directory included on your command path. To test this, issue a "ant -version" command from your shell and verify that Ant is available.
3. Download the Apache Solr source distribution, linked from the above incubator web site. Expand the distribution to a folder of your choice, e.g. c:solr.
4. Navigate to that folder and issue an "ant" command to see the available options for building, testing, and packaging solr.
Enhancements:
- This is the first release since graduating from the Apache Incubator.
- Some of the new features include CSV/delimited-text data loading, time based autocommit, faster faceting, negative filters, a spell-check handler, sounds-like word filters, regex text filters, and more flexible plugins.

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 mod_suid allows per-vhost execution of scripts under their own UIDs. It functions in a way similar to Apaches perchild MPM, but differs in a number of ways.

Apache mod_suid does per child user/group switching; the Apache MPM makes switches based on vhosts. All processing is done under a specific UID/GID, including PHP and mod_perl scripts.

Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java.
Apache Lucene is a technology suitable for nearly any application that requires full-text search, especially cross-platform.
Enhancements:
- Many new features, optimizations, and bugfixes have been added since 2.1.0, including "point-in-time" searching over NFS, payloads, function queries, and new APIs for pre-analyzed fields.
- This release includes index format changes that are not readable by older versions.
- It can both read and update older Lucene indexes.
- Adding to an index with an older format will cause it to be converted to the newer format.

Apache::TestMB is a subclass of Module::Build to support Apache::Test.

SYNOPSIS

Standard process for building & installing modules:
perl Build.PL
./Build
./Build test
./Build install

Or, if youre on a platform (like DOS or Windows) that doesnt like the "./" notation, you can do this:

perl Build.PL
perl Build
perl Build test
perl Build install

This class subclasses Module::Build to add support for testing Apache integration with Apache::Test. It is broadly based on Apache::TestMM, and as such adds a number of build actions to a the Build script, while simplifying the process of creating Build.PL scripts.

Heres how to use Apache::TestMB in a Build.PL script:

use Module::Build;

my $build_pkg = eval { require Apache::TestMB }
? Apache::TestMB : Module::Build;

my $build = $build_pkg->new(
module_name => My::Module,
);
$build->create_build_script;

This is identical to how Module::Build is used. Not all target systems may have Apache::Test (and therefore Apache::TestMB installed, so we test for it to be installed, first. But otherwise, its use can be exactly the same. Consult the Module::Build documentation for more information on how to use it; Module::Build::Cookbook may be especially useful for those looking to migrate from ExtUtils::MakeMaker.

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.