view release on metacpan or  search on metacpan

lib/Apache/AuthTicket.pm  view on Meta::CPAN

=head2 Apache Configuration - httpd.conf

There are two ways that this module could be configured.  Either by using a
function call in startup.pl, or by configuring each handler explicitly in
httpd.conf.  If you decide to mix and match using calls to Apache::AuthTicket->configure() with directives in httpd.conf, then remember that the following precedence applies:

 o If a directive is specified in httpd.conf, it will be used.
 o else if a directive is specified by configure(), then the 
   configure() value will be used.
 o else a default value will be used.

 view release on metacpan or  search on metacpan

AuthenLDAP.pm  view on Meta::CPAN

#   implied warranties or conditions of merchantability and fitness
#   for a particular purpose;
#
#   ii) effectively excludes on behalf of all Contributors all
#   liability for damages, including direct, indirect, special,
#   incidental and consequential damages, such as lost profits;
#   iii) states that any provisions which differ from this Agreement
#   are offered by that Contributor alone and not by any other party;
#   and
#
#   iv) states that source code for the Program is available from such

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

  A README file is required for CPAN modules since CPAN extracts the
  README file from a module distribution so that people browsing the
  archive can use it get an idea of the modules uses. It is usually a
  good idea to provide version information here so that people can
  decide whether fixes for the module are worth downloading.
]


INSTALLATION

 view release on metacpan or  search on metacpan

smb/.svn/text-base/Changes.svn-base  view on Meta::CPAN

0.2  Thu Jul 30 20:46:00 1998
	- no real changes, some minor documentation updates.  First CPAN
	  release.

0.3  Sun Aug  2 13:58:00 1998
	- Removed the object files that accidentally got left in smbval/

0.4  Thu Mar  4 16:20:00 1999
	- Fixed the versioning in Smb.pm so that CPAN clients will download
          the correct version.

 view release on metacpan or  search on metacpan

AuthzCache.pm  view on Meta::CPAN

#   implied warranties or conditions of merchantability and fitness
#   for a particular purpose;
#
#   ii) effectively excludes on behalf of all Contributors all
#   liability for damages, including direct, indirect, special,
#   incidental and consequential damages, such as lost profits;
#   iii) states that any provisions which differ from this Agreement
#   are offered by that Contributor alone and not by any other party;
#   and
#
#   iv) states that source code for the Program is available from such

 view release on metacpan or  search on metacpan

AuthzLDAP.pm  view on Meta::CPAN

#   implied warranties or conditions of merchantability and fitness
#   for a particular purpose;
#
#   ii) effectively excludes on behalf of all Contributors all
#   liability for damages, including direct, indirect, special,
#   incidental and consequential damages, such as lost profits;
#   iii) states that any provisions which differ from this Agreement
#   are offered by that Contributor alone and not by any other party;
#   and
#
#   iv) states that source code for the Program is available from such

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

inc/Module/Install.pm  view on Meta::CPAN

use strict 'vars';

use vars qw{$VERSION};
BEGIN {
    # All Module::Install core packages now require synchronised versions.
    # This will be used to ensure we don't accidentally load old or
    # different versions of modules.
    # This is not enforced yet, but will be some time in the next few
    # releases once we can make sure it won't clash with custom
    # Module::Install extensions.
    $VERSION = '0.68';

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

configuration/dbconf/globalconf.pl  view on Meta::CPAN

# and the DBI execute has returned with failure, then the rollback is in effect.

# The caller can always catch and check the return value of a DBI::BabyConnect method
# to see if it has failed a DBI execute. Typically DBI::BabyConnect methods return undef
# whenever a DBI execute fails and therefore the caller can check the return
# value and decide on whether to call the DBI::BabyConnect object method rollback himself or not,
# therefore allowing the caller to continue to work with the instance of DBI::BabyConnect object 
# and its open DBI connection.
# Yet, you can configure the behavior of the DBI::BabyConnect object methods globally
# and tell the object methods to automatically rollback and exit on failure.

# This option is settable and will work only if AutoRollback is in effect for the
# DBI, because DBI::BabyConnect objects delegate all rollbacks to the DBI itself.
# DBI rollback is in effect if and only if:
#  RaiseError is 0 (it should be off because otherwise the DBI would have exited earlier due to the error)
#  AutoCommit is 0 (DBI will have no effect on rollback is AutoCommit is set to 1)
# DBI::BabyConnect will keep track of the success or failure of DBI execute(), hence deciding on
# what to do on failure.
#
# DBI will not exit if the conditions on the rollback are not met, but it will
# continue without effectively rolling back.
#

 view release on metacpan or  search on metacpan

Backhand.pm  view on Meta::CPAN

=over 3

=item mtime

Last modification time of this stat structure (the last time we heard from
the server - used to decide if the server is alive)

=item arriba

Speed of the server

 view release on metacpan or  search on metacpan

Blog.pm  view on Meta::CPAN

All diary entries are stored as plain text files, there's no database
stuff going on here. This is to make it simple to add entries - any
editor can be used to write entries.

To use, decide on a directory which is to hold your weblog entries,
and set PerlHandler like in the example. The alias isn't nessasary,
but I like it that way.

Also in that directory need to be two template files, one called
entry-template.html, and one called older.html.

 view release on metacpan or  search on metacpan

lib/Apache/Bootstrap.pm  view on Meta::CPAN

    my $env = exists $ENV{MOD_PERL} ? $ENV{MOD_PERL} : 0;

    # check for contradicting requirements
    if ( $env && $flag && $flag != $env ) {
        warn <<EOF;
Can\'t decide which mod_perl version should be used, since you have
supplied contradicting requirements:
    enviroment variable MOD_PERL=$env
    Makefile.PL option  MOD_PERL=$flag
EOF
        die;

 view release on metacpan or  search on metacpan

inc/Module/Install.pm  view on Meta::CPAN

use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.
	$VERSION = '1.00';

 view release on metacpan or  search on metacpan

Centipaid.pm  view on Meta::CPAN

Centipaid.com offers websites the flexibility to charge small amounts
of money, also refered to as B<micropayment>, to users wishing to
access to their web services without the complexity of setting up 
e-commerce enabled site, or to deal with expensive credit card 
processing options. Users benefit from not having to reveal their
identity or credit card information everytime they decide to visit a 
website.  Instead, centipaid allows users to simply pay using
a pre-paid internet stamp, by simply uploading the stamp to centipaid's
site. The stamps are valid in all sites using centipaid.com payment
system.

Centipaid.pm  view on Meta::CPAN

=item B<enforce_ip> 0

 This tells the module if the website wants to tie
 the receipt to a one ip.  This may be requiered in
 certain casees where the site admin decides that
 access to the site is made only from the ip of
 the machine that makes the payment, as long as the
 machine also holds the receipt cookie.  The valid 
 values are 0 for "do not restrict to ip", and 1 
 for "yes do restrict to the ip".  If ommited, then

Centipaid.pm  view on Meta::CPAN

==end

where B<rcpt> stores the recipt number, B<date> and B<expire> contain the date the
receipt was issued on the site, and its expiration. B<Paid> contains the amount paid
in float format.  The B<IP> could be used in cases where the site admin decides to tie
a payment to an ip as well as a browser.  We do not reommend this, since people use 
proxy servers, and dynamic IPs.  The B<zone> is used for statistical purposes, where
the website admin can see what sections are being used most.

 view release on metacpan or  search on metacpan

Compress.pm  view on Meta::CPAN

}

sub can_gzip {
  my $r = shift;

  my $how_decide = $r->dir_config('CompressDecision');
  if (!defined($how_decide) || lc($how_decide) eq 'header') {
    return +($r->header_in('Accept-Encoding')||'') =~ /gzip/;
  } elsif (lc($how_decide) eq 'user-agent') {
    return guess_by_user_agent($r->header_in('User-Agent'));
  }
  
  die "Unrecognized value '$how_decide' specified for CompressDecision";
}
  
sub guess_by_user_agent {
  # This comes from Andreas' Apache::GzipChain.  It's very out of
  # date, though, I'd like it if someone sent me a better regex.

Compress.pm  view on Meta::CPAN

=head1 SYNOPSIS

  PerlModule Apache::Compress
  
  # Compress regular files - decides whether to compress by
  # examining the Accept-Encoding header
  <FilesMatch "\.blah$">
   SetHandler perl-script
   PerlHandler Apache::Compress
  </FilesMatch>

 view release on metacpan or  search on metacpan

CompressClientFixup.pm  view on Meta::CPAN

=head2 Microsoft Internet Explorer

Internet Explorer sometimes loses the first 2048 bytes of data
that are sent back by Web Servers that use HTTP compression,
- Microsoft confirms for MSIE 5.5 in Microsoft Knowledge Base Article - Q313712
(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q313712).

The similiar statement about MSIE 6.0 is confirmed in Microsoft Knowledge Base Article - Q312496.

In accordance with Q313712 and Q312496, these bugs affect transmissions through

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

  When we speak of free software, we are referring to freedom of use,

LICENSE  view on Meta::CPAN

such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

 view release on metacpan or  search on metacpan

t/httpd02.conf  view on Meta::CPAN

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution
system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through
that system in reliance on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.

 view release on metacpan or  search on metacpan

GPL  view on Meta::CPAN

such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    command before returning the actual handle to the user. Hence, with
    Apache::DBI::Cache many the overall number of connections to a DB server
    can be dramatically reduced.

  HOW DOES IT WORK?
    To decide whether to use Apache::DBI::Cache or not it is essential to
    know how it works. As with Apache::DBI Apache::DBI::Cache uses a hook
    provided by the DBI module to intercept "DBI->connect()" calls. Also do
    Apache::DBI::Cache maintain a cache of active handles.

    When a new connection is requested and the cache is empty a new

 view release on metacpan or  search on metacpan

lib/Apache/AuthDBI.pm  view on Meta::CPAN

=item * Auth_DBI_authoritative  < on / off> (Authentication and Authorization)

Default is 'on'. When set 'on', there is no fall-through to other
authentication methods if the authentication check fails. When this directive
is set to 'off', control is passed on to any other authentication modules. Be
sure you know what you are doing when you decide to switch it off.

=item * Auth_DBI_nopasswd  < on / off > (Authentication only)

Default is 'off'. When set 'on' the password comparison is skipped if the
password retrieved from the database is empty, i.e. allow any password.
This is 'off' by default to ensure that an empty Auth_DBI_pwd_field does not 
allow people to log in with a random password. Be sure you know what you are 
doing when you decide to switch it on.

=item * Auth_DBI_encrypted  < on / off > (Authentication only)

Default is 'on'. When set to 'on', the password retrieved from the database
is assumed to be crypted. Hence the incoming password will be crypted before

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

that should be provided before the module is installed.

A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it get an idea of the modules uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.

INSTALLATION

To install this module, run the following commands:

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

  When we speak of free software, we are referring to freedom of use,

LICENSE  view on Meta::CPAN

such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.

INSTALLATION

To install this module type the following:

 view release on metacpan or  search on metacpan

lang/br.lang  view on Meta::CPAN

		'LOGIN_BUTTON'      => 'Entrar',
		'PAGE_LOGIN'        => 'Página de Login',
		'LOGIN_NOTE'        => 'Nota: Configure seu Navegador para Aceitar Cooks para poder se logar. Sua Senha Será Solicitada depois de algum tempo.',
		'IDLE_TIMEOUT'      => 'Motivo da Desconexãoao: Tempo Esgotado',
		'MALFORMED_TICKET'  => 'Motivo da Desconexão: Ticket com Malformação',
		'INVALID_HASH'      => 'Motivo da Desconexão: Ticket Desconhecido',
		'EXPIRED_TICKET'    => 'Motivo da Desconexão: Ticket Expirou',
		'MISSING_SECRET'    => 'Motivo da Desconexão: Server secret não pode ser carregado',
		'TAMPERED_HASH'     => 'Motivo da Desconexão: Ticket dados alterados com',
		'PASSWORD_CHANGE'   => 'A senha só será alterada se você digitar algo nos campos abaixo.'
		);