Free apache 2.2 ssl software for linux

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 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::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-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::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::MP3 is a Perl module that can generate streamable directories of MP3 and Ogg Vorbis files.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg mp3 MP3
AddType audio/playlist m3u M3U
AddType audio/x-scpls pls PLS
AddType application/x-ogg ogg OGG

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3
< /Location >

# Or use the Apache::MP3::Sorted subclass to get sortable directory listings
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Sorted
< /Location >

# Or use the Apache::MP3::Playlist subclass to get persistent playlists
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Playlist
< /Location >
A demo version can be browsed at http://www.modperl.com/Songs/.

This module makes it possible to browse a directory hierarchy containing MP3, Ogg Vorbis, or Wav files, sort them on various fields, download them, stream them to an MP3 decoder like WinAmp, and construct playlists. The display is configurable and subclassable.

NOTE: This version of Apache::MP3 is substantially different from the pre-2.0 version described in The Perl Journal. Specifically, the format to use for HREF links has changed. See Linking for details.

Apache Ant is a Java based build tool, similar to make, but with better support for the cross platform issues involved with developing Java applications.
Apache Ant is the build tool of choice for all Java projects at Apache and many other Open Source Java projects.
Enhancements:
- A resource framework was introduced.
- Some of the core ant tasks such as copy are now able to process not only file system resources but also zip entries, tar entries, and paths.
- Resource collections group resources, and can be further combined with operators such as union and intersection.
- This version starts outsourcing of optional tasks to Antlibs.
- The .NET antlib replaces the .NET optional tasks.
- Support for the version control system Subversion is also provided as an antlib.
- A large number of bugs were fixed.
- Some initial support for Java6 features was added.