Result:
found more than 871 distributions - search limited to the first 2001 files matching your query
( run in 1.079 )
Apache-AxKit-Language-XSP-ObjectTaglib
view release on metacpan or search on metacpan
lib/Apache/AxKit/Language/XSP/ObjectTaglib.pm view on Meta::CPAN
This comes from a wrapper around LDAP. As before, the C<person> tag at
the top level has two subroutines to set up the C<person> target.
(which in this case will be C<$_xsp_axkit_xsp_ldap_person>) When a
C<name> tag is seen inside of the C<person> tag, a method is called on
that target. This time, we use C<key> to say that the method name is
actually C<cn>, rather than C<name>. Hence the following XSP:
<b:person dn="foo">
<b:name/>
</b:person>
Apache-ErrorControl
view release on metacpan or search on metacpan
ErrorControl.pm view on Meta::CPAN
</TMPL_IF>
=item *
B<error_notes> - the error-notes (C<$r-E<gt>prev()-E<gt>notes('error-notes')>,
see L<Apache>). this is more useful in say a staging environment that has
mod_perl applications. it is the error message, for mod_perl applications
it includes the complete error message but for normal cgi applications
it just includes 'premature end of script headers'.
<TMPL_IF NAME="error_notes">
Apache-Filter
view release on metacpan or search on metacpan
lib/Apache/Filter.pm view on Meta::CPAN
of its input file (whether the $r->filename file or the output of another filter),
and doesn't depend at all on outside factors. For example, a filter that translates
all its output to upper-case is deterministic, but a filter that adds a date
stamp to a page, or looks things up in a database which may vary over time, is not.
Why is this a big deal? Let's say you have the following setup:
<Files ~ "\.boffo$">
SetHandler perl-script
PerlSetVar Filter On
PerlHandler Apache::FormatNumbers Apache::DoBigCalculation
lib/Apache/Filter.pm view on Meta::CPAN
current filter is the last filter, the headers will be sent as usual,
and otherwise send_http_header() is a no-op.
=head1 NOTES
You'll notice in the SYNOPSIS that I say C<"PerlSetVar Filter On">. That
information isn't actually used by this module, it's used by modules which
are themselves filters (like Apache::SSI). I hereby suggest that filtering
modules use this parameter, using it as the switch to detect whether they
should call $r->filter_register. However, it's often not necessary -
there is very little overhead in simply calling $r->filter_register
Apache-HeavyCGI
view release on metacpan or search on metacpan
lib/Apache/HeavyCGI.pm view on Meta::CPAN
The three big tasks a CGI script has to master are Headers, Parameters
and the Content. In general one can say, content creation SHOULD not
start before all parameters are processed. In complex scenarios you
MUST expect that the whole layout may depend on one parameter.
Additionally we can say that some header related data SHOULD be
processed very early because they might result in a shortcut that
saves us a lot of processing.
Consequently, Apache::HeavyCGI divides the tasks to be done for a
request into four phases and distributes the four phases among an
Apache-ImageMagick
view release on metacpan or search on metacpan
ImageMagick.pm view on Meta::CPAN
The parameters for the C<Set> method a prefixed with C<Set:>
http://localhost/images/whatever.jpg/Frame/Shade?Frame:color=gold&Shade:color=true&Set:quality=10
The C<AIMParameter> configuration diretive can be used to set defaults and/or force
parameters values. So you can say
PerlSetVar AIMParameter "font=/usr/images/fonts/arial.ttf !color=red"
By prefixing the parameter with an !, the parameter values is foreced, so it
can't be overridden by parameters passed to the hanlder via th URI.
Apache-LoggedAuthDBI
view release on metacpan or search on metacpan
Binding an C<undef> (NULL) to the placeholder will I<not> select rows
which have a NULL C<age>! At least for database engines that
conform to the SQL standard. Refer to the SQL manual for your database
engine or any SQL book for the reasons for this. To explicitly select
NULLs you have to say "C<WHERE age IS NULL>".
A common issue is to have a code fragment handle a value that could be
either C<defined> or C<undef> (non-NULL or NULL) at runtime.
A simple technique is to prepare the appropriate statement as needed,
and substitute the placeholder for non-NULL cases:
=head2 Signal Handling and Canceling Operations
[The following only applies to systems with unix-like signal handling.
I'd welcome additions for other systems, especially Windows.]
The first thing to say is that signal handling in Perl versions less
than 5.8 is I<not> safe. There is always a small risk of Perl
crashing and/or core dumping when, or after, handling a signal
because the signal could arrive and be handled while internal data
structures are being changed. If the signal handling code
used those same internal data structures it could cause all manner
Apache-MONITOR
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
TEST_F = test -f
TOUCH = touch
UMASK_NULL = umask 0
DEV_NULL = > /dev/null 2>&1
# The following is a portable way to say mkdir -p
# To see which directories are created, change the if 0 to if 1
MKPATH = $(PERLRUN) "-MExtUtils::Command" -e mkpath
# This helps us to minimize the effect of the .exists files A yet
# better solution would be to have a stable file in the perl
Apache-OWA
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
TEST_F = test -f
TOUCH = touch
UMASK_NULL = umask 0
DEV_NULL = > /dev/null 2>&1
# The following is a portable way to say mkdir -p
# To see which directories are created, change the if 0 to if 1
MKPATH = $(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) -MExtUtils::Command -e mkpath
# This helps us to minimize the effect of the .exists files A yet
# better solution would be to have a stable file in the perl
Apache-PageKit
view release on metacpan or search on metacpan
- Fixed usage of Digest::MD5::md5_hex in sub pkit_auth_credential and
pkit_auth_session_key in Common.pm (Boris Zentner)
- Set Default for the server attrs can_edit and reload (Boris Zentner)
- First attempt to make pkit warning clean (Boris Zentner, David Raimbault)
- Fix default timeout for 'recent_login_timeout' from unlimited to 3600
like the Docs say (Boris Zentner)
- Parse difficult parameters like
http://ka.brain.de/login2?passwd=ss&&&&submit&&login=s& (Boris Zentner)
- Add restricted page to the example site (Boris Zentner)
- Fixed setup_session without touch of pkit_merge_session (Boris Zentner)
- Fixed problem with append of check_cookie (Boris Zentner)
Apache-ParseFormData
view release on metacpan or search on metacpan
was changed to Apache::OK).
Thanks to Finn Hakansson <finn@df.lth.se>
0.07 Wed Jul 30 11:29:29 WEST 2003
- fixed documentation where it saids "Apache::Request" starts to
say "Apache::ParseFormData"
Thanks to Stas Bekman <stas@stason.org>
0.06 Fri Jul 25 15:39:30 WEST 2003
- a small bug in "parse_content" was fixed
- the documetation has been updated
Apache-Reload
view release on metacpan or search on metacpan
lib/Apache2/Reload.pm view on Meta::CPAN
C<L<ModPerl::Registry|docs::2.0::api::ModPerl::Registry>> but not
C<L<ModPerl::PerlRun|docs::2.0::api::ModPerl::PerlRun>>.
=head3 The Problem
Let's say that there is a module C<My::Utils>:
#file:My/Utils.pm
#----------------
package My::Utils;
BEGIN { warn __PACKAGE__ , " was reloaded\n" }
Apache-SdnFw
view release on metacpan or search on metacpan
lib/Apache/SdnFw/js/tinymce/jscripts/tiny_mce/tiny_mce_src.js view on Meta::CPAN
// Store away text range for next call
lastIERng = selection.getRng();
}
// IE will say that the range is equal then produce an invalid argument exception
// if you perform specific operations in a keyup event. For example Ctrl+Del.
// This hack will invalidate the range cache if the exception occurs
try {
range.startContainer.nextSibling;
} catch (ex) {
Apache-SecSess
view release on metacpan or search on metacpan
over intranets. Under the stronger threat model of an active adversary
who controls the untrusted network, true end-to-end security is
required, but we may still wish to separate session and authentication
qualities of protection. For example, if all SSL sessions never drop
below 128-bits, we may still choose to allow weaker strength during user
authentication, say with a 20-bit PIN or one-time password. Scientific
cryptography cannot always afford to distinguish between an attack which
costs 2^20 computations and one which succeeds with probability 1/2^20,
because with 1 million users, the two situations are identical. But, for
practical risk assessment, it may be perfectly acceptable to trade strong
session credentials for weak login credentials.
<Location /authen>
PerlAuthenHandler $Acme::stu->issue
...
</Location>
where $Acme::stu is an instance of, say Apache::SecSess::Cookie::X509,
just as in the previous example.
But if and when cookies are present, $Acme::chain->issue will walk
through the URL's listed in the chainURLS argument eventually getting
to https://noam.acme.org/authen protected by
Apache-SessionX
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
print "\n" ;
print "You can now specify the configuration parameters for every storage.\n" ;
print "Apache::SessionX uses this for testing your system and stores it for later\n" ;
print "use in your application. You can override these default parameters anytime\n" ;
print "at runtime. You can change them by rerunning Makefile.PL.\n" ;
print "\nIf you don't plan to use different storages for session, \nonly say Yes to the one storage you want to use.\n" ;
foreach $store (@avail)
{
print "\n" ;
$data = $Store{$store} ;
Apache-SetWWWTheme
view release on metacpan or search on metacpan
templates/LookAndFeelConfig view on Meta::CPAN
# Put this file into any directory, and it will affect any file within
# that directory and all of its subdirectories. These files are good
# for setting a look and feel for a set of physically related files.
# For example, say you have a directory of files all on one subject, and
# you decide they should all have a blue background. You could go
# something like this:
@BGCOLOR=#9999FF;
Apache-SiteConfig
view release on metacpan or search on metacpan
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
if( $self->{args}->{su} ) {
$cmd = sprintf( 'sudo -u %s %s', $self->{args}->{su} , $cmd );
}
say $cmd;
if( $abort_on_failure ) {
system( $cmd ) == 0 or die $!;
} else {
system( $cmd );
}
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
}
sub clean {
my $self = shift;
my $args = $self->preprocess_meta;
say "Cleanning up $args->{site_dir}";
rmtree( $args->{site_dir} );
}
sub update {
my $self = shift;
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
SKIP_SOURCE_CLONE:
if( $args->{source} ) {
if( $args->{source}->{git} ) {
last SKIP_SOURCE_CLONE if -e File::Spec->join( $args->{site_dir} , '.git' );
say "Cloning git repository from $args->{source}->{git} to $args->{site_dir}";
$self->execute_command("git clone $args->{source}->{git} $args->{site_dir}",1);
# if branch is specified, then check the branch out.
my $branch = $args->{source}->{branch};
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
}
elsif( $args->{source}->{hg} ) {
last SKIP_SOURCE_CLONE if -e File::Spec->join( $args->{site_dir} , '.git' );
say "Cloning hg repository from $args->{source}->{hg} to $args->{site_dir}";
$self->execute_command("hg clone $args->{source}->{hg} $args->{site_dir}") == 0 or die($?);
}
}
$self->prepare_log_path( $args );
if( $args->{chown} ) {
say "Changing owner to $args->{site_dir}";
$self->execute_command( sprintf( 'chown -R %s: ' , $args->{site_dir} ) ,1);
}
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
my $config_content = $context->to_string;
# get site config directory
my $apache_dir_debian = '/etc/apache2/sites-available';
if( -e $apache_dir_debian ) {
say "Apache Site Config Dir Found.";
my $config_file = File::Spec->join( $apache_dir_debian , $args->{name} );
if ( -e $config_file ) {
say "$config_file exists, skipped.";
} else {
say "Writing site config to $config_file.";
open my $fh , ">", $config_file;
print $fh $config_content;
close $fh;
say "Enabling $args->{name}";
system("a2ensite $args->{name}");
say "Reloading apache";
system("/etc/init.d/apache2 reload");
}
}
else {
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
my $apache_dir = dirname(dirname( $apachectl_bin ));
my $apache_conf_dir = File::Spec->join( $apache_dir , 'conf' );
if( -e $apache_conf_dir ) {
say "Found apache configuration directory: $apache_conf_dir";
# prepare site config dir
mkpath [ File::Spec->join( $apache_conf_dir , 'sites' ) ];
my $httpd_conf = File::Spec->join( $apache_conf_dir , 'httpd.conf' );
# write site config to apache conf dir
my $config_file = File::Spec->join( $apache_conf_dir , 'sites' , $args->{name} . '.conf' );
say "Writing config file: $config_file";
open my $fh , ">" , $config_file or die $!;
print $fh $config_content;
close $fh;
say "Appending Include statement to $httpd_conf";
open my $fh2 , ">>" , $httpd_conf or die $!;
print $fh2 "###### Apache Site Configurations \n";
print $fh2 "Include conf/sites/$args->{name}.conf\n";
close $fh2;
lib/Apache/SiteConfig/Deploy.pm view on Meta::CPAN
# TODO: run apache configtest here
# /opt/local/apache2/bin/apachectl -t -f /path/to/config file
my $config_file = File::Spec->join( 'apache2' , 'sites' , $args->{name} ); # apache config
mkpath [ File::Spec->join('apache2','sites') ];
say "Writing site config file: $config_file";
open my $fh , ">", $config_file or die "Can not write config file $config_file: $!";
print $fh $config_content;
close $fh;
}
Apache-SiteControl
view release on metacpan or search on metacpan
lib/Apache/SiteControl.pm view on Meta::CPAN
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.
lib/Apache/SiteControl.pm view on Meta::CPAN
makes calls like:
if($referee->can($userA, "beat up", $userB)) { ... }
In terms of English, we would describe the rule "If A is taller than B, then
we say that A can beat up B. If A is less skilled than B, then we say that
A cannot beat up B". The rule looks like this:
package samples::FightRules;
use strict;
Apache-Storage
view release on metacpan or search on metacpan
Ever wanted to store information in Apache so
the additional requests could gain access to it?
For example, you create an object which is fairly
expensive and you don't want to have to
recreate each time, or say you just have some
information you are storing in a reference that
you want requests that follow you to see.
This module is for you.
Apache-Test
view release on metacpan or search on metacpan
lib/Apache/Test.pm view on Meta::CPAN
since the test will be skipped, unless all the rules are satisfied,
it's not equivalent for the end users. The second technique, deploying
C<need()> and a list of requirements, always runs all the requirement
checks and reports all the missing requirements. In the case of the
first technique, if the first requirement fails, the second is not
run, and the missing requirement is not reported. So let's say all the
requirements are missing Apache modules, and a user wants to satisfy
all of these and run the test suite again. If all the unsatisfied
requirements are reported at once, she will need to rebuild Apache
once. If only one requirement is reported at a time, she will have to
rebuild Apache as many times as there are elements in the C<&&>
Apache-TopicMaps
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
TEST_F = test -f
TOUCH = touch
UMASK_NULL = umask 0
DEV_NULL = > /dev/null 2>&1
# The following is a portable way to say mkdir -p
# To see which directories are created, change the if 0 to if 1
MKPATH = $(PERLRUN) "-MExtUtils::Command" -e mkpath
# This helps us to minimize the effect of the .exists files A yet
# better solution would be to have a stable file in the perl
Apache-Voodoo
view release on metacpan or search on metacpan
lib/Apache/Voodoo/Table.pm view on Meta::CPAN
# if we're sorting on the same key as before, then we have the chance to go descending
if ($sort eq $last_sort) {
if ($desc eq '1') {
$q =~ s/,/ DESC, /g;
$q .= " DESC";
$n_desc = 0; # say that we are ascending the next time.
}
else {
$n_desc = 1; # say that we are descending the next time.
}
}
else {
$n_desc = 1; # we just sorted ascending, so now we need to say to sort descending
$desc = 0;
}
$select_stmt .= "ORDER BY $q\n";
}
Apache-WAP-AutoIndex
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
TEST_F = test -f
TOUCH = touch
UMASK_NULL = umask 0
DEV_NULL = > /dev/null 2>&1
# The following is a portable way to say mkdir -p
# To see which directories are created, change the if 0 to if 1
MKPATH = $(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) -MExtUtils::Command -e mkpath
# This helps us to minimize the effect of the .exists files A yet
# better solution would be to have a stable file in the perl
Apache-WAP-MailPeek
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
TEST_F = test -f
TOUCH = touch
UMASK_NULL = umask 0
DEV_NULL = > /dev/null 2>&1
# The following is a portable way to say mkdir -p
# To see which directories are created, change the if 0 to if 1
MKPATH = $(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) -MExtUtils::Command -e mkpath
# This helps us to minimize the effect of the .exists files A yet
# better solution would be to have a stable file in the perl
Apache-WebDAV
view release on metacpan or search on metacpan
lib/Apache/WebDAV.pm view on Meta::CPAN
#
# Update: I found it in a proposal here:
#
# http://www.greenbytes.de/tech/webdav/draft-ietf-webdav-quota-07.html
#
# But it doesn't say anything about quota, quotaused, or
# quota-assigned-bytes - I found out that webdrive was looking for those
# from its log file.
my $quota = $doc->createElement('D:quota');
my $quota_used = $doc->createElement('D:quotaused');
my $quota_available_bytes = $doc->createElement('D:quota-available-bytes');
Apache-Wyrd
view release on metacpan or search on metacpan
Wyrd/Site/Index.pm view on Meta::CPAN
=item (objectref) C<ua> (hashref)
Another over-loadable handle. Should return a handle to a LWP useragent
object (See LWP::UserAgent) appropriate for navigating the site, which is to
say it should have some way of handling access and authentication
appropriate to the site's construction. There is no default ua; the
webmaster will need to define it in order to use this object.
Note that this method is required by Apache::Wyrd::Services::IndexBot.
Apache2-API
view release on metacpan or search on metacpan
lib/Apache2/API.pm view on Meta::CPAN
my $hash = apr1_md5( $clear_password );
my $hash = apr1_md5( $clear_password, $salt );
my $ht = $api->htpasswd( $clear_password );
my $ht = $api->htpasswd( $clear_password, salt => $salt );
my $hash = $ht->hash;
say "Does our password match ? ", $ht->matches( $user_clear_password ) ? "yes" : "not";
=head1 VERSION
v0.5.3
lib/Apache2/API.pm view on Meta::CPAN
=head1 CONSTANTS
C<mod_perl> provides constants through L<Apache2::Constant> and L<APR::Constant>. L<Apache2::API> makes all those constants available using their respective package name, such as:
use Apache2::API;
say Apache2::Const::HTTP_BAD_REQUEST; # 400
You can import constants into your namespace by specifying them when loading L<Apache2::API>, such as:
use Apache2::API qw( HTTP_BAD_REQUEST );
say HTTP_BAD_REQUEST; # 400
Be careful, however, that there are over 400 Apache2 constants and some common constant names in L<Apache2::Constant> and L<APR::Constant>, so it is recommended to use the fully qualified constant names rather than importing them into your namespace.
Some constants are special like C<OK>, C<DECLINED> or C<DECLINE_CMD>
Apache2-ASP
view release on metacpan or search on metacpan
conjunction with RequestFilters.
1.28 2008-02-06
- Added $Response->Decline and changed the return value of $Response->End
and $Response->Redirect to 0 and 302 respectively.
- Now inside RequestFilters you can simply say 'return $Response->Declined'
or 'return $Response->Redirect("/mypage.asp")' to exit the RequestFilter.
- Documentation for RequestFilters and Response needs to be updated to
reflect this change.
1.27 2008-02-06
Apache2-AuthEnv
view release on metacpan or search on metacpan
lib/Apache2/AuthEnv.pm view on Meta::CPAN
Some systems may take authentication information from various sources
and provide different environment variables for each source. So you can
list alternative variables to use.
AuthEnvUser %{HTTP_SOURCE1_NAME|HTTP_SOURCE2_NAME|HTTP_SOURCE3_NAME}
If nothing matches then you can set a default value (say 'anon') via
AuthEnvUser %{HTTP_SOURCE_NAME|HTTP_SOURCE2_NAME:anon}
For nested directives, configurations are inherited from one
configuration file to the next. I<AuthEnvUser> directives overwrite each
other as do collections of I<AuthEnvAllow*> rules. Each individual
Apache2-AuthNetLDAP
view release on metacpan or search on metacpan
AuthNetLDAP.pm view on Meta::CPAN
require valid-user
PerlAuthenHandler Apache2::AuthNetLDAP
If you don't have mod_perl or Net::LDAP installed on your system, then the Makefile will prompt you to
install each of these modules. At this time, March 8, 2004, you may say yes to Net::LDAP, and yes for
mod_perl, if you are installing this module on apache 1.3. (The reason being, that mod_perl 2 is under
development, and is not ready for download from CPAN at this time. Therefore, your install of mod_perl,
as initiated with the Makefile.PL, will fail. If you are going to install mod_perl 2, which is needed
to work with Apache2, you will need to download it from: http://perl.apache.org/download/index.html.
(Installation is beyond the scope of this document, but you can find documentation at:
Apache2-Authen-Passphrase
view release on metacpan or search on metacpan
my $passwd = prompt 'Enter new Apache2::Authen::Passphrase password: ';
my $confirm = prompt 'Retype new Apache2::Authen::Passphrase password: ';
die "Sorry, passwords do not match\n" unless $passwd eq $confirm;
pwset $username, $passwd;
say 'Password updated successfully'; ## no critic (RequireCheckedSyscalls)
__END__
=head1 NAME
( run in 1.079 second using v1.01-cache-2.11-cpan-d7a12ab2c7f )