Result:
found more than 1316 distributions - search limited to the first 2001 files matching your query
( run in 1.943 )
Apache-Access-Headers
view release on metacpan or search on metacpan
=over 3
=item B<ALL>
If the <id> of a <header> block is 'ALL', then _all_ requests for resources
matched by the attached <path> tags. This is useful for allowing access
to <path>/</path> and <path>index.html</path>, etc.
=back
=over 3
Apache-Album
view release on metacpan or search on metacpan
# For detailed information on this module, please see
# the pod data at the bottom of this file
#
# Copyright 1998-2004 James D Woodgate. All rights reserved.
# It may be used and modified freely, but I do request that this copyright
# notice remain attached to the file. You may modify this module as you
# wish, but if you redistribute a modified version, please attach a note
# listing the modifications you have made.
use Image::Magick;
use vars qw($VERSION);
Apache-App-Mercury
view release on metacpan or search on metacpan
$self->{compose_msg}->{'sent_to'} = $self->{user_manager}->userprofile('user');
$self->{compose_msg}->{'recipient_desc'} = $self->{user_manager}->userprofile('user_desc');
} elsif ($q->param('nonmemo')) {
$self->{compose_msg}->{'sent_to'} = '';
$self->{compose_msg}->{'recipient_desc'} = '';
} elsif (defined (my $attach_no = $q->param('remove_attach'))) {
splice(@{$self->{compose_msg}->{'Attachments'}}, $attach_no, 1);
}
$self->show_mail_compose;
} elsif ($self->{'state'} eq 'preview_message') {
if defined $q->param('recipient');
$self->{compose_msg}->{'subject'} = $q->param('subject')
if defined $q->param('subject');
$self->{compose_msg}->{'body'} = $q->param('body')
if defined $q->param('body');
$self->{compose_msg}->{'num_to_attach'} =
$q->param('num_files_to_attach')
if defined $q->param('num_files_to_attach');
$self->{compose_msg}->{'security'} = $q->param('security')
if defined $q->param('security');
}
sub reset_compose_message {
my $q = $self->{q};
my $compose = $self->{compose_msg};
my $is_memo = ($compose->{'sender'} eq $compose->{'sent_to'});
# add to msg object new attachments from CGI POST data that browser sent
$compose->read_attachments_from_cgi;
# tell message object to store itself
if ($compose->store) {
$self->{controller}->infomsg(!$is_memo ? "Your message has been sent." : "Your memo has been committed.");
delete $self->{compose_msg};
sent_to varchar(255) DEFAULT '' NOT NULL,
sender varchar(16) DEFAULT '' NOT NULL,
timestamp timestamp(14),
subject varchar(100),
body text,
attachments text NOT NULL,
status enum('unread','read','replied','forwarded','deleted') DEFAULT 'unread',
status_sender enum('unread','read','replied','forwarded','deleted') DEFAULT 'unread',
status_smtp enum('unsent','sent','checked') DEFAULT 'unsent' NOT NULL,
code varchar(15) DEFAULT '' NOT NULL,
box varchar(16) DEFAULT '' NOT NULL,
KEY sent_to (sent_to(34)),
KEY trans (trans),
KEY status_smtp (status_smtp)
);
CREATE TABLE message_attachments (
aid int(10) unsigned DEFAULT '0' NOT NULL auto_increment,
filesys char(255) DEFAULT '' NOT NULL,
attachment char(255) DEFAULT '' NOT NULL,
msg_ids char(255) DEFAULT '' NOT NULL,
PRIMARY KEY (aid),
UNIQUE filesys (filesys)
);
Apache-AppSamurai
view release on metacpan or search on metacpan
examples/conf/appsamurai-owa.conf view on Meta::CPAN
# the FQDN of your server to its real IP address inside your network.
# 3) Basic Authentication must be configured (Form based login breaks
# ActiveSync. This config is for a Basic Auth backend only.)
# 4) You should be able to use OWA (https://servername.domain/exchange/)
# from inside your network.
# 5) You should be able to use ActiveSync with a device attached to your
# internal network. (Microsoft's Windows Mobile emulator is helpful
# for testing.)
#
# For your AppSamurai server:
# 1) You must have a SSL certificate signed by a trusted CA.
Apache-AuthChecker
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-AuthCookie
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-AuthCookieDBI
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-AuthCookieDBIRadius
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-AuthCookieLDAP
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-AuthCookiePAM
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-AuthTicket
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-AuthenNTLM
view release on metacpan or search on metacpan
AuthenNTLM.pm view on Meta::CPAN
. " cuser = " . $r -> user . ' remote_ip = ' . $conn -> remote_ip
. " remote_port = " . unpack('n', $port) . ' remote_host = <'
. $conn -> remote_host . "> version = $VERSION "
. "smbhandle = " . $self -> {smbhandle} . "\n" if ($debug) ;
# we cannot attach our object to the connection record. Since in
# Apache 1.3 there is only one connection at a time per process
# we can cache our object and check if the connection has changed.
# The check is done by slightly changing the remote_host member, which
# persists as long as the connection does
# This has to be reworked to work with Apache 2.0
Apache-AxKit-Provider-OpenOffice
view release on metacpan or search on metacpan
dtds/chart.mod view on Meta::CPAN
chart:data-point* )>
<!ATTLIST chart:series
chart:values-cell-range-address %cell-range-address; #IMPLIED
chart:label-cell-address %cell-address; #IMPLIED
chart:class %chart-class; #IMPLIED
chart:attached-axis %string; #IMPLIED
chart:style-name %styleName; #IMPLIED >
<!ELEMENT chart:domain EMPTY>
<!ATTLIST chart:domain
table:cell-range-address %cell-range-address; #IMPLIED >
Apache-Backhand
view release on metacpan or search on metacpan
Backhand.pm view on Meta::CPAN
both reads and writes) into the shared memory segment where serverstats
resides. You can call load_serverstats() once, and use the returned structure
as much as you want - it will always reflect the contents of the underlying
shared structure. This has one drawback, however, which is that you cannot
call load_serverstats() until after the shared memory segment has been created
and attached. I recommend a PerlChildInit handler to do load_serverstats()
into a global variable.
=item B<load_personal_arriba>
This function returns a reference to a scalar variable which is magically
Backhand.pm view on Meta::CPAN
As explained above, you cannot PerlModule or use() or require()
Apache::Backhand until *after* mod_backhand (and mod_perl, of course) are
linked into the server.
As explained above, you cannot call load_serverstats() until *after* the
shared memory segment has been created and attached. The best place to do
this is the child init phase.
It's easy to make mod_backhand coredump by doing Bad Things to serverstats
(e.g. 'foreach (@{$serverstats}) { $_->{'mtime'} = time() }'...)
Even though I've provided the magic to make serverstats writeable, this should
Apache-BalancerManager
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-Bootstrap
view release on metacpan or search on metacpan
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
Apache-Config-Preproc
view release on metacpan or search on metacpan
lib/Apache/Config/Preproc/locus.pm view on Meta::CPAN
$self->context_pop();
return 0;
}
}
# Compute and attach a locus object.
$self->{line}++;
my $locus = new Text::Locus($self->filename, $self->{line});
if ($d->type eq 'section') {
$self->lpush($locus);
} elsif ($d->type eq 'directive') {
lib/Apache/Config/Preproc/locus.pm view on Meta::CPAN
1;
__END__
=head1 NAME
Apache::Config::Preproc::locus - attach file location to each parse node
=head1 SYNOPSIS
$x = new Apache::Config::Preproc '/path/to/httpd.conf',
-expand => [ qw(locus) ];
lib/Apache/Config/Preproc/locus.pm view on Meta::CPAN
print $_->locus
}
=head1 DESCRIPTION
B<Locus> attaches to each node in the parse tree a B<Text::Locus> object
which describes the location of the corresponding statement in the source
file. The location of a node can be accessed via the B<locus> method
as illustrated in the synopsis.
Technically speaking, this module replaces each instance of
Apache-CryptHash
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-Defaults
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-EmbeddedPerl-Lite
view release on metacpan or search on metacpan
ApacheSoftwareLicense view on Meta::CPAN
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
ApacheSoftwareLicense view on Meta::CPAN
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
Apache-ErrorControl
view release on metacpan or search on metacpan
ErrorControl.pm view on Meta::CPAN
'Requested URL: '. $request_url. "\n".
'Requested By: '. $requestor. "\n\n".
"--------------------\n".
"Apache::ErrorControl\n\n";
$mobj->attach(
Data => $body,
Type => 'text/plain'
);
# Construct Included Debug
ErrorControl.pm view on Meta::CPAN
);
foreach my $file (keys %files) {
my $string = $self->apache_table_to_string($files{$file});
if ($string) {
$mobj->attach(
Data => $string,
Filename => $file. '.txt',
Type => 'text/plain',
Encoding => 'base64'
);
ErrorControl.pm view on Meta::CPAN
=head1 ERROR EMAILS
This module has the ability to send an email on an error. you can define
what error code to email on and what email addresses to send emails to, please
see the B<OPTIONS> section on how to do this. the error email contains various
attached files and these are present in the email depending on weather or not
their data could be retrieved. the attached files are detailed below.
=over 4
=item *
ErrorControl.pm view on Meta::CPAN
=back
=head2 EXAMPLE EMAIL
Below is an example email (obviously missing the file attachments).
Subject: Error 500 on www.abc.com
Time: 2004-05-05 14:27:22
Requested URL: http://www.abc.com/testing/testing123.cgi
Apache-ExtDirect
view release on metacpan or search on metacpan
lib/Apache/ExtDirect/Router.pm view on Meta::CPAN
return $postdata ne '' ? $postdata
: undef
;
};
# If any files are attached, extUpload will contain 'true'
my $has_uploads = $cgi->param('extUpload') eq 'true';
# Here file uploads data is stored
my @_uploads = ();
Apache-FakeCookie
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-FastForward
view release on metacpan or search on metacpan
lib/Apache/FastForward.pm view on Meta::CPAN
=head1 COPYRIGHT
Copyright 2006 Jerzy Wachowiak <jwach@cpan.org>
This library is free software; you can redistribute it and/or modify
it under the terms of the Apache 2.0 license attached to the module.
=head1 SEE ALSO
L<Apache::FastForward::Spreadsheet>
Apache-GopherHandler
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-HTMLView
view release on metacpan or search on metacpan
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
Apache-Htaccess
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-Htpasswd
view release on metacpan or search on metacpan
Htpasswd.pm view on Meta::CPAN
=head1 AUTHOR INFORMATION
Copyright 1998..2005, Kevin Meltzer. All rights reserved. It may
be used and modified freely, but I do request that this copyright
notice remain attached to the file. You may modify this module as you
wish, but if you redistribute a modified version, please attach a note
listing the modifications you have made.
This is released under the same terms as Perl itself.
Address bug reports and comments to:
Apache-Log-Parser
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
Apache-LogFormat-Compiler
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
( run in 1.943 second using v1.01-cache-2.11-cpan-e1769b4cff6 )