view release on metacpan or search on metacpan
lib/Apache/TestRunPHP.pm view on Meta::CPAN
<?php
print "1..1\n";
print "ok 1\n"
?>
if it looks odd, that's ok because it is. I could explain to you exactly
what this means, but it isn't important to understand the gory details.
instead, it is sufficient to understand that when C<Apache::Test> calls
C<bar.php> it feeds the results directly to C<Test::Harness>, a module
that comes with every Perl installation, and C<Test::Harness> expects
what it receives to be formated in a very specific way. by itself, all
view release on metacpan or search on metacpan
javascript.pod view on Meta::CPAN
want to muck with the UploadMeter object to get around this, just create an empty
DIV on your page, set the style to hidden (eg, display: none), and pass that to
the UploadMeter object. If you do wish to use this built-in object, ensure that
the CSS class of this div is "uploadmeter" (and don't hide it!)
Also, it is worth noting that the default behavior looks for an element class
named "uploadform" and attempts to add to the onSubmit code for it, to trigger
the bundled default pop-up window. If you don't want this to happen, just run:
C<Event.stopObserving(aum_el, 'submit', aum_popup);>
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
eval { require mod_perl };
eval { require mod_perl2 } if ($@);
die "Can't find mod_perl installed\nThe error was: $@" if $@;
}
# the function looks at %ENV and Makefile.PL option to figure out
# whether a specific mod_perl generation was requested.
# It uses the following logic:
# via options:
# perl Makefile.PL MOD_PERL=2
# or via %ENV:
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
eval { require mod_perl };
die "Can't find mod_perl installed\nThe error was: $@" if $@;
}
# the function looks at %ENV and Makefile.PL option to figure out
# whether a specific mod_perl generation was requested.
# It uses the following logic:
# via options:
# perl Makefile.PL MOD_PERL=2
# or via %ENV:
view release on metacpan or search on metacpan
lib/Apache/WebDAV.pm view on Meta::CPAN
In order to get a working WebDAV server up and running quickly, the following instructions are provided. It is recommended that you install Filesys::Virtual::Plain and follow the instructions below. Please be advised that there is no authentication...
=head2 mod_perl handler
My theoretical server is "myserver" in all examples. First you need to write a simple mod_perl handler. Mine is called DAVHandler.pm. The code looks like this:
package DAVHandler;
use strict;
use warnings;
view release on metacpan or search on metacpan
Wyrd/Input.pm view on Meta::CPAN
=pod
=item (void) C<_parse_options> (void)
_parse_options looks to the B<options> attribute, which may be explicit
as a comma/whitespace delineated list or built up by sub-objects (see
C<Apache::Wyrd::Input::Opt>) in order to determine what options to give
to the datum object. If this value is already a hashref or arrayref, it
does no further processing. Otherwise it attempts to separate the words
of the options attribute, using an optional regexp under the "delimiter"
view release on metacpan or search on metacpan
man/xpptagtut.pod view on Meta::CPAN
called C<@parsers> that contains the names of all the parser methods you're
creating to handle your custom tags. Each tag will have exactly one parser
method associated with it. The second step is to implement those parser methods
for your custom tags.
The beginning of our Apache::XPP::PreParse subclass looks like this:
package My::XPP::PreParse;
use strict;
use Apache::XPP::PreParse;
view release on metacpan or search on metacpan
lib/Apache/iNcom.pm view on Meta::CPAN
if ( $cookies->{INCOM_SESSION} ) {
my $session_id = $cookies->{INCOM_SESSION}->value;
# Load the user's session
eval {
# Make sure it looks like a session id
die "Invalid session id: $session_id\n"
unless length $session_id == 32 &&
$session_id =~ tr/a-fA-F0-9/a-fA-F0-9/ == 32;
tie %session, 'Apache::iNcom::Session', $session_id,
view release on metacpan or search on metacpan
lib/Apache2/API/DateTime.pm view on Meta::CPAN
Provided with a date string, and this will parse it and return a L<DateTime> object, or sets an L<error|Module::Generic/error> and return C<undef> or an empty list depending on the context.
=head2 str2datetime
Given a string that looks like a date, this will parse it and return a L<DateTime> object.
=head2 str2time
Given a string that looks like a date, this returns its representation as a unix timestamp in second since epoch.
In the background, it calls L</str2datetime> for parsing.
=head2 time2datetime
view release on metacpan or search on metacpan
lib/Apache2/ASP/ErrorHandler.pm view on Meta::CPAN
sub run {
my ($s, $context) = @_;
my $error = $Stash->{error};
# $error looks like this:
$VAR1 = {
title => 'Cannot call execute with a reference',
file => '/tmp/PAGE_CACHE/mysite/index_asp.pm',
line => 45,
stacktrace => # Output from Carp::confess,
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/Apache2/AuthCookieDBI.pm view on Meta::CPAN
my $auth_name = $r->auth_name;
my $session_key;
# Check that this looks like an encrypted hex-encoded string.
if ( $encrypted_session_key !~ HEX_STRING_REGEX ) {
my $message
= "${class}\tencrypted session key '$encrypted_session_key' doesn't look like it's properly hex-encoded for auth realm $auth_name";
$class->logger( $r, Apache2::Const::LOG_ERR, $message, undef,
LOG_TYPE_SYSTEM, $r->uri );
view release on metacpan or search on metacpan
lib/Apache2/AuthCookieDBImg.pm view on Meta::CPAN
inssert into images (imageurl,imageword) values ('/images/dbimg/junk.png','saywhat?');
Then create an image named junk.png and put it in my web server /images/dbimg folder.
The text on the image has a background picture plus the word "saywhat?" across the front.
The randomizer just looks up the imageurl and imagekey in the database and spits out
the appropriate HTML code. ApacheCookieDBImg then does a reverse operation, looking
up the imageword based on the key.
=head1 CAVEATS
lib/Apache2/AuthCookieDBImg.pm view on Meta::CPAN
# Decrypt the session key.
my $session_key;
if ( $c{ DBI_encryptiontype } eq 'none' ) {
$session_key = $encrypted_session_key;
} else {
# Check that this looks like an encrypted hex-encoded string.
unless ( $encrypted_session_key =~ /^[0-9a-fA-F]+$/ ) {
$r->log_error( "Apache2::AuthCookieDBImg: encrypted session key $encrypted_session_key doesn't look like it's properly hex-encoded for auth realm $auth_name", $r->uri );
return undef;
}
view release on metacpan or search on metacpan
AuthTicketLDAP.pm view on Meta::CPAN
Keep in mind that the mmap caching will make apache processes look huge. It is
an illusion -- cached files are only mapped into memory once.
LDAP authentication processing works similarly to mod_ldap/mod_authnz_ldap.
1) An anonymous search looks up a user on the LDAP server.
Returns 403 if unsuccessful. Otherwise, the entry is cached.
2) That user's LDAP entry DN and password is used to bind to
the server. Returns 403 if unsuccessful, OK if successful.
On the database side, everything works the same as I<Apache2::AuthTicket> except
view release on metacpan or search on metacpan
lib/Apache2/Authen/OdinAuth.pm view on Meta::CPAN
The handler reads (and automatically reloads if it's older than
C<reload_timeout> seconds) an additional YAML config file. It sets
configures the shared secret, cookie name, authorizer app URL, and
permissions (which are unfortunately regexp-based).
A sample configuration file looks like this:
# Sample config for Apache2::Authen::OdinAuth
permissions:
# URLs no auth
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/Apache2/Controller.pm view on Meta::CPAN
}
}
For instance
L<Apache2::Controller::Render::Template> implements
C<< error() >> for you, which looks for
the appropriately named error template as
F<template_dir/errors/###.html>.
Of course, all exceptions are sent to the error log using
L<Log::Log4perl> DEBUG() before the handler completes, and
lib/Apache2/Controller.pm view on Meta::CPAN
use YAML::Syck;
use Digest::SHA qw( sha224_base64 );
use URI;
use HTTP::Status qw( status_message );
use Scalar::Util qw( looks_like_number );
use Apache2::Controller::X;
use Apache2::Controller::Funk qw( log_bad_request_reason );
use Apache2::Request;
lib/Apache2/Controller.pm view on Meta::CPAN
# by your A2C dispatch handler:
MyApp::Controller::Foo->handler( Apache2::RequestRec object )
The handler is pushed from an Apache2::Controller::Dispatch
subclass and via your dispatched subclass of Apache2::Controller.
It should not be set in the config file. It looks
for the controller module name in C<< $r->pnotes->{a2c}{controller} >>
and for the method name in C<< $r->pnotes->{a2c}{method} >>.
Errors are intercepted and if the handler object was created
and implements an C<< $handler->error($exception) >> method
lib/Apache2/Controller.pm view on Meta::CPAN
my $args = $pnotes_a2c->{path_args} || [];
$status = $handler->$method(@{$args});
$status = $r->status() if !defined $status;
if (defined $status) {
if (ref $status || !looks_like_number($status)) {
a2cx message => "Controller returned or set non-numeric status",
status => Apache2::Const::SERVER_ERROR,
dump => { controller_set_status => $status };
}
elsif ($status < 0) {
view release on metacpan or search on metacpan
- remove -RC\d+
- add release date
b. rerun:
% perl Makefile.PL
make sure tag looks right
% make -n tag
c. commit Changes
% svn ci Changes
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/Apache2/HttpEquiv.pm view on Meta::CPAN
=head1 DESCRIPTION
Apache2::HttpEquiv provides a PerlFixupHandler for mod_perl 2 that turns
C<< <meta http-equiv="Header-Name" content="Header Value"> >> into an actual
HTTP header. It also looks for C<< <meta charset="..."> >> and uses it to
set the Content-Type to C<text/html; charset=...>.
If the file claims its Content-Type is 'text/xhtml', the Content-Type
is set to 'text/html' instead. 'text/xhtml' is not a valid
Content-Type, and any file that claims it is probably too broken to
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
database and sends a temporary redirect to the browser. It also
intercepts the following request from the browser and sends the stored
reply.
How it works
This module inserts an request output filter that looks for replies for
POST requests with a HTTP code of 200. If it finds one it saves the
reply in a database and replaces the complete output with a temporary
redirect (HTTP code 302) to the same URL but with a special marked query
string appended.
view release on metacpan or search on metacpan
docsrc/features.xml view on Meta::CPAN
configuration options.
</para>
<para>
To create a new view, create a <filename>View/<replaceable>pkit_view</replaceable></filename> directory and place the PageKit Templates and XSLT files for
the pages and components that you wish to apply the view to. Note that if
PageKit doesn't find a template or XSLT file in the <filename>View/<replaceable>pkit_view</replaceable></filename> directory it looks in the
<filename>View/Default</filename> directory. That is, the files <filename>View/<replaceable>pkit_view</replaceable></filename> "override" the files
in <filename>View/Default</filename> directory.
</para>
<para>
To association a media output such as XML, WML, or PDF with a view, use
view release on metacpan or search on metacpan
lib/Apache2/SSI.pm view on Meta::CPAN
sub _is_perl_script
{
my $self = shift( @_ );
my $file = shift( @_ );
return( $self->error( "No file was provided to check if it looks like a perl script." ) ) if( !length( "$file" ) );
if( -T( "$file" ) )
{
my $io = IO::File->new( "<$file" ) || return( $self->error( "Unable to open file \"$file\" in read mode: $!" ) );
my $shebang = $io->getline;
chomp( $shebang );
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
lib/Apache2/SiteControl.pm view on Meta::CPAN
=head2 PERMISSION MANAGER
Each site will have a permission manager. There is usually no need for you
to subclass Apache2::SiteControl::PermissionManager, but you do need to create one
and populate it with your access rules. You do this by creating a
factory class, which looks something like this:
package samples::site::MyPermissionFactory;
use Apache2::SiteControl::PermissionManager;
use Apache2::SiteControl::GrantAllRule;
lib/Apache2/SiteControl.pm view on Meta::CPAN
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;
use warnings;
view release on metacpan or search on metacpan
similar to a condition, only its value is ignored. Record 4 then checks
if the "Host" header matches "/de$/". If so, then record 5 sets the
*language* to "de".
Now, the records labeled with ":PRE:" are finished. The handler starts
looking for blocks labeled with the request uri. That is, it looks for a
block with key=front, uri=/static/img.png. None is found.
Then it cuts off the last part of the uri (/img.png), repeats the lookup
and finds record 6. The "File" action sets "$r->filename" to
"$DOCROOT/en/img.png". "Apache2::Translation" provides some convenience
place. To make things even more confusing some directives take
effect at several points in time. Consider
Options FollowSymLinks ExecCGI
"FollowSymLinks" is applied when Apache looks up a file in the file
system, while "ExecCGI" influences the way the response is generated
ages later.
Apache solves this complexity by computing a configuration for each
single request. As a starting point it uses the server default