Free apache 13 permission denied software for linux

Apache XML Projects goals are:
- to provide commercial-quality standards-based XML solutions that are developed in an open and cooperative fashion,
- to provide feedback to standards bodies (such as IETF and W3C) from an implementation perspective, and
- to be a focus for XML-related activities within Apache projects
The Apache XML Project used to be the home for many XML-related subprojects, many of which have moved to top-level project status recently or are currently in migration. The Apache XML Project slowly transforms into an place where you can find pointers to XML-related projects here in the Apache Software Foundation. The remaining subprojects directly under the supervision of the XML PMC are:
- AxKit - XML-based web publishing, in mod_perl
- Crimson - A Java XML parser derived from the Sun Project X Parser.
- Xang - Rapid development of dynamic server pages, in JavaScript
- Xindice - A native XML database.
- XML Commons - focussed on common code and guidelines for XML projects
- XML Security - Java and C++ implementations of the XML signature and encryption standards

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 Graffito provides a framework used to build content-based applications.

Graffito is a framework used to build content-based applications like CMSs, document management systems, forums, blogs, etc. It offers a complete platform for creating, managing, and publishing content in your portal or in any other kind of Java application.

It integrates content repositories, workflow, collaboration, and personalization via existing open source projects and standards like WEBDAV.

Apache LDAP vhost driver project lets you put vhost with all possible information in an LDAP database for both Apache 1.x and 2.x.

Bug report system

With the new maintainence, there is now also a bug report system at the URL http://bugs.bayour.com/ (project mod_ldap_cfg).

Schemas

A schema called mod_ldap_cfg is used.

Apache config

To setup Apache to use this module, the httpd.conf is used.

Apache::MP3::Skin is a subclass of Apache::MP3::Playlist with the ability to "skin" the output using HTML::Template.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg .mp3 .MP3

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Skin
PerlSetVar HomePath /songs # optional
PerlSetVar DefaultSkin default.tmpl # required

# Without DefaultSkin being set to a valid file
# Apache::MP3::Skin will be the same as Apache::MP3
< /Location >

Apache::MP3::Skin subclasses Apache::MP3::Playlist enabling the use of skin files which are html files with special tags enabled by HTML::Template. See Apache::MP3 for details on installing and using.

AntUnit is a library of Ant tasks that was initially developed to write tests for Ant tasks without resorting to JUnit. Apache AntUnit makes it easy to turn an existing build file that exhibits an error into an AntUnit test.

Tests are written as targets in a build file using assertion tasks provided by AntUnit. The antunit task executes targets in a collection of build files and supports custom listeners in a manner similar to the junit tasks formatters.

Apache::SiteControl is a Perl web site authentication/authorization system.

SYNOPSIS

See samples/site for complete example. Note, this module is intended for mod_perl. See Apache2::SiteControl for mod_perl2.

Apache::SiteControl is a set of perl object-oriented classes that implement a fine-grained security control system for a web-based application. The intent is to provide a clear, easy-to-integrate system that does not require the policies to be written into your application components. It attempts to separate the concerns of how to show and manipulate data from the concerns of who is allowed to view and manipulate data and why.

For example, say your web application is written in HTML::Mason. Your individual "screens" are composed of Mason modules, and you would like to keep those as clean as possible, but decisions have to be made about what to allow as the component is processed. SiteControl attempts to make that as easy as possible.

DEVELOPERS VIEWPOINT - EXAMPLE

In this document we use HTML::Mason to create examples of how to use the control mechanisms, but any mod_perl based system should be supportable.

A good mason component tries to do most of the perl processing in a separate block, so that simple substitutions can be made in HTML in the rest of the page. This makes it much easier for web developers and perl developers to co-exist on a project.

The SiteControl system tries to make it possible to continue to follow this model. You obtain a user object and permission manager from the SiteControl system. These are intended to be opaque data types to the page designer, and are defined elsewhere (see USERS). The actual web page component should carry these objects around without implementing anything in the way of policy.