I think these are good points.
However, to some degree, if this is an attempt to allow an ISP protection,
it's not because most ISPs offer CGI access to their customers.
In addition, the moment you give mod_perl access to a developer they have
the rights to do a LOT of stuff that goes beyond
At 08:43 PM 11/15/00 +0300, Ilya Martynov wrote:
On 15 Nov 2000, David Hodgkinson wrote:
DH Stas Bekman [EMAIL PROTECTED] writes:
DH
DH Ralf is always talking about SSL stuff, so if you want to do it, why
don't
DH you just contact him and sync with him. It's not mod_perl but many of us
DH
Hey,
I'm working on a new module to be used for mod_perl style
caching. I'm calling it MLDBM::Sync because its a subclass
of MLDBM that makes sure concurrent access is serialized with
flock() and i/o flushing between reads and writes. Below is
the code for the module. I believe it could
Hi,
Going along ths lines of sharing mod_perl between users for ISPs
is there a median position that tempers security concerns/support
costs/hassles etc that a CPAN module could fill?
I'm thinking of a module like APache::Registry but it segments the
namespace/memory
On Fri, 17 Nov 2000, Nigel Hamilton wrote:
Going along ths lines of sharing mod_perl between users for ISPs
is there a median position that tempers security concerns/support
costs/hassles etc that a CPAN module could fill?
I wouldn't do it like that.
I'm thinking of a
At 11:15 AM 11/17/00 +, Matthew Byng-Maddick wrote:
On Fri, 17 Nov 2000, Nigel Hamilton wrote:
Going along ths lines of sharing mod_perl between users for ISPs
is there a median position that tempers security concerns/support
costs/hassles etc that a CPAN module could fill?
On Fri, 17 Nov 2000, Gunther Birznieks wrote:
At 11:15 AM 11/17/00 +, Matthew Byng-Maddick wrote:
man jail() on FreeBSD 4.
But then you lose the benefits of having shared apache processes among many
shared users many of whom may have very non-busy web sites. No?
Yes, but this is the
Hello everyone,
I`m writing a module to process templates on which our web server is
built. This module is invoked during PerlInitHandler. We have a
global configuration for our site which is a plain text file
containing a hash like this:
{
bgcolor = '',
I assume your using apache_1.3.14 and mod_perl-1.24. You need
mod_perl-1.24_01. It will work. I had the same problem.
Kevin Riggins
Dice.com
email: [EMAIL PROTECTED]
email: [EMAIL PROTECTED]
phone: (515) 313-2127
-Original Message-
From: James Hall [mailto:[EMAIL PROTECTED]]
Sent:
The -Wl flag is used to cause the rpath part to be passed on the ld
stage of compiling if it is called with cc. The man pages for cc explain it
in better detail. The problem is that the Makefile for mod_perl in
$APACHE_SRC/src/modules/perl calls ld directly and the -Wl flag is not
supported
on 11/17/00 8:10 AM, [EMAIL PROTECTED] at [EMAIL PROTECTED] uttered the
following:
supported by ld. In order to get it to compile I edited
$APACHE_SRC/src/modules/perl/Makefile after running configure and added the
-rpath stuff without the comma to the LDFLAGS variables and removed all
Gunther Birznieks wrote:
It seems to me that mod_perl wasn't really designed for safety against your
own developers
I accept this point. But it's really beside _my_ point, which was that
mod_perl modules can offer critical added functionality to run-of-the-mill
web publishers (whether it
on 11/17/00 8:35 AM, [EMAIL PROTECTED] at [EMAIL PROTECTED] uttered the
following:
When building static, I use the following:
Configuring and compile mod_perl:
$ perl Makefile.PL \
APACHE_SRC=../apache_x.x.x/src \
USE_APACI=1 \
DO_HTTPD=1 \
EVERYTHING=1 \
PREP_HTTPD=1
$ make
That's
"Richard" == Richard L Goerwitz [EMAIL PROTECTED] writes:
Richard I simply want to be able to do the same thing in Perl with mod_perl. I
Richard want to be able to give developers ("users" - whatever you want to call
Richard them) added functionality, without giving them the ability to execute
"Randal L. Schwartz" wrote:
Use Template Toolkit, and disable the "EVAL_PERL" option for their space.
Set up Plugins and Filters that call your Cool Perl Code.
Then they write arbitary text files to be delivered...
Suppose it were possible to set Perl-based modules to work the same way
C
barries [EMAIL PROTECTED] wrote:
On Fri, Nov 17, 2000 at 03:51:35PM +1100, Steve Smith wrote:
seek $f, 0, 0;
Had a look in Apache::File (below), and it sysopens, so you might want
to sysseek(...) instead.
Just to clear up one thing: sysopen() doesn't actually belong to the
sys* family
On Fri, Nov 17, 2000 at 03:51:03PM +0100, Roger Espel Llima wrote:
Internally sysopen() does a plain libc
open(), but then it follows with a fdopen() call to get a stdio handle
anyway.
That explains the results I saw, thanks.
- Barrie
Hey Friends,
I have two ORACLE_HOME directories in my client
machine (7.2.2 and 8.0.5). When I set ENV to 8.0.5 or
7.2.2, this seems there no effect. Also when I use the
connection like this :
$dbh = DBI-connect("DBI:Oracle:$sid", "$username",
"$password",
{ RaiseError = 1, AutoCommit = 0
I'm trying to configure a single box to host completely separate instances
of development and test versions of the same code base (currently 49
modules).
Right now I have 2 virtual hosts configured on the same IP and servername,
but use different ports, i.e., 80 and 82.
I attempted to use
I'm trying to configure a single box to host completely separate instances
of development and test versions of the same code base (currently 49
modules).
Right now I have 2 virtual hosts configured on the same IP and servername,
but use different ports, i.e., 80 and 82.
The only way I
Hello all,
I'm a newbie to mod_perl, and I have a question. We have mod_perl on our
server, but it is a standard out of the box install (Only PerlHandler is
enabled.) Now, I'd like to use .htaccess files to test some stuff out
(no dev server either) and I don't want to be
I'd have no problem if mod_perl was set up to turn off
PerlSetEnv, lit-
eral 'sub { ... }' handlers, Perl sections, and the use of
Perl modules
in non-system paths (except where ExecCGI is turned on).
Maybe another approach would be to explicitly list the handlers that
are allowed to be
This is what we do. Except we use the SAME config file, but we just have some
conditionals that depend on which port number is being started up.
-c
At 3:47 PM + 11/17/00, [EMAIL PROTECTED] wrote:
I'm trying to configure a single box to host completely separate instances
of development
I have a program which runs fine 90% of the time under mod_perl. About 10% of
the time Netscape reports "Document contains no data". Looking at the socket
traffic, the client receives an orderly release indication (T_ORDEL_IND = 132)
on the socket and reponds with a orderly release request,
Scott Dayberry ([EMAIL PROTECTED]) said something to this effect:
I'm trying to configure a single box to host completely separate instances
of development and test versions of the same code base (currently 49
modules).
Right now I have 2 virtual hosts configured on the same IP and
On 17 Nov 2000, Stephen A. Cochran wrote:
I have a program which runs fine 90% of the time under mod_perl. About 10% of
the time Netscape reports "Document contains no data". Looking at the socket
traffic, the client receives an orderly release indication (T_ORDEL_IND = 132)
on the socket
Say I have a $Directory{} configuration in a Perl section like so:
$Directory{"/home/httpd/html-ssl/demo"} = {
SetHandler = "perl-script",
PerlAuthenHandler = "Authen",
PerlAuthzHandler = "Authz",
require = "group payer_manager",
require = "payer_group
I think require = ["group payer_manager", "payer_group demo"] should do it.
On Fri, Nov 17, 2000 at 01:11:09PM -0500, Adi Fairbank wrote:
Say I have a $Directory{} configuration in a Perl section like so:
$Directory{"/home/httpd/html-ssl/demo"} = {
SetHandler = "perl-script",
I suspect that this has something to do with using Perl 5.6.0. I and several
others have had problems getting mod_perl to work with this version of Perl under
various flavors of Unix (Solaris, AIX, HP-UX). We have all also found that if you
roll Perl back to 5.005 that this appears to solve the
mgraham wrote:
Maybe another approach would be to explicitly list the handlers that
are allowed to be used in any given context. Kind of
like 'Options', but for perl handlers. Something like 'PerlOptions',
perhaps?
Location /users
PerlOptions "My::AuthHandler My::ContentHandler
on 11/17/00 1:20 PM, Jimi Thompson at [EMAIL PROTECTED] uttered the
following:
I suspect that this has something to do with using Perl 5.6.0. I and several
others have had problems getting mod_perl to work with this version of Perl
under
various flavors of Unix (Solaris, AIX, HP-UX). We
"Richard" == Richard L Goerwitz [EMAIL PROTECTED] writes:
Richard That's a neat idea.
Richard The only quibble I can think of is that this doesn't go far enough.
Richard This lower level of privilege we're talking about is one in which -
Richard 1) Only specific Perl modules are available
Hi,
just use magic...:
1. move your test modules to /path/TEST/YourPrefix/name.pm
2. add /path to @INC (NOT /path/TEST !)
3. add PerlSetVar test TRUE for your test virtual host and change the
PerlHandlers to read TEST::YourPrefix::name
4. write a Filter that does something like
if
Howdy,
I have an application that's pure mod_perl -- its modules use the request
object to do a few bits of work like reading parameters, query string,
specialized logging, dealing with NOT_MODIFIED, and so on. Normal stuff
provided by the methods of Apache, Apache::Util, Apache::URI and
More troubles in this saga to install mod_perl with apache:
After building mod_perl static with apache on DU4.0b and getting no errors
(so far), I tried the same thing on Tru64 5.1 and I'm still getting this:
ld -shared -expect_unresolved "*" -O4 -msym -std -s -L/usr/local/lib -o
libperl.so
Try getting rid of Perl 5.6 and using 5.005. This has worked for me and for
several other folks running other flavors of Unix.
Didier Godefroy wrote:
More troubles in this saga to install mod_perl with apache:
After building mod_perl static with apache on DU4.0b and getting no errors
(so
On Fri, Nov 17, 2000 at 11:53:05AM -0800, Bill Moseley wrote:
Now, I'd like to use a few of my modules under CGI -- for an administration
part of the application that's bigger and not used enough to use up space
in the mod_perl server. But it would be nice to have a common code base.
One
ld -shared -expect_unresolved "*" -O4 -msym -std -s -L/usr/local/lib -o
For whatever reason, it's trying to build a dso. I'd double check my
settings.
Kevin Riggins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
on 11/17/00 3:48 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] uttered the
following:
ld -shared -expect_unresolved "*" -O4 -msym -std -s -L/usr/local/lib -o
For whatever reason, it's trying to build a dso. I'd double check my
settings.
You were right, it must be because I had
"Randal L. Schwartz" wrote:
I think y'all are missing it. As soon as I have any Perl code access
via Apache::Registry or anything like that, I can do this:
*Apache::Registry::handler = \my_trojan_horse;
Can you explain in what server-configuration context the above directive
would
I'm working on an apache configuration script, and I'm having trouble with
the enabling of perl-status, server-info, etc.
I modified the examples in the eg directory, so I have:
my %handlers = (
"/perl-status" = "Apache::Status",
);
for (keys %handlers) {
$Location{$_} = {
"Adi Fairbank" [EMAIL PROTECTED] wrote:
No I tried that (sorry I should have said so). I think:
Perl
$Location{"blah"} = {
require = ["group payer_manager", "payer_group demo"]
};
/Perl
is equivalent to:
Location "blah"
require group payer_manager payer_group demo
/Location
Hi all again,
I was trying to add the Apache::Scoreboard module to perl using cpan and
it's giving out errors:
cc: Error:
/usr/local/lib/perl5/site_perl/5.6.0/alpha-dec_osf/auto/Apache/include/inclu
de/http_protocol.h, line 153: Invalid declara
tion.
Dave Kaufman wrote:
i belive it is. in fact, i didn't realize specifing two require coditions (one
group and one user) worked on *separate* lines :)
something like:
$Location{"blah"} = {
require = "group payer_manager, payer_group demo"
};
should do the trick.
-dave
Thanks,
To reply to my own messages...
These work fine in the httpd.conf with a Perl section, but I was trying to
do it in a separate startup script. I'm just going to move my code back to
the main conf file for now.
--
Barry Hoggard
Chief Technology Officer
http://www.investorama.com
v: 212.905.1639
Dave Kaufman wrote:
i belive it is. in fact, i didn't realize specifing two require coditions (one
group and one user) worked on *separate* lines :)
something like:
$Location{"blah"} = {
require = "group payer_manager, payer_group demo"
};
should do the trick.
-dave
I wrote:
"Adi Fairbank" [EMAIL PROTECTED] wrote:
Dave Kaufman wrote:
$Location{"blah"} = {
require = "group payer_manager, payer_group demo"
};
should do the trick.
I wrote:
Thanks, that fixed it.
Actually, no that didn't fix it!
$r-requires
returns
[{ 'group' =
On Fri, 17 Nov 2000, Jimi Thompson wrote:
Try getting rid of Perl 5.6 and using 5.005. This has worked for me and for
several other folks running other flavors of Unix.
Weird, but compiled 5.6 perl with default options does not mesh well with
mod_perl, however I run Mandrake Linux, and 5.6
Here is an other one:
I finally got mod_perl statically compiled and installed with apache.
I didn't run the tests on mod_perl as they fail every time, maybe it has
something to do with what's going on now, I'm not sure. When I try to run
one of those test scripts that come with apache in the
Bill Moseley wrote:
Howdy,
I have an application that's pure mod_perl -- its modules use the request
object to do a few bits of work like reading parameters, query string,
specialized logging, dealing with NOT_MODIFIED, and so on. Normal stuff
provided by the methods of Apache,
50 matches
Mail list logo
