stas2003/02/04 20:06:28
Modified:.Changes
ModPerl-Registry/lib/ModPerl RegistryCooker.pm
ModPerl-Registry TODO
Log:
warn on using -T in ModPerl::Registry scripts when mod_perl is not
running with -T
Revision ChangesPath
1.122
alrightly, back again. The problem is that Apache::Registry will return
a 206, which will trigger the error message. In case there is anyone
out there as daft as me :), the crude delegation-type module below can
solve this problem. Maniacs who see a need to return 204's, etc can
probably
OpenBSD 3.2
Perl 5.6.1
I'm trying to build MP 1.99_08 for Apache 2.0.44, and I'm not quite
sure where I'm messing up. Apache built fine, building the config for
MP went fine:
jweisen@kaitain$ sudo perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2
MP_INST_APACHE2=1
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
Hi Stas,
On Tuesday, February 4, 2003 at 2:47:43 AM, you wrote:
SB Lee Goddard wrote:
SB [...]
I don't know: you're doing this:
print Content-type: text/plain\n\n;
print Hello World\n;
Does it (probably not) make any difference if
you do a
Hi,
I have written a request handler in Perl. I recently changed some code
in this to convert
from using CGI within mod_perl to using Apache::Registry. The old code
was ...
$DB-{ApacheReq} = shift;
:
$DB-{Page} = CGI::new();
:
The new code is ...
:
$DB-{ApacheReq}=
I, rather blindly, put a reference to a hash of the HTTP headers and hash of
the CGI params in pnotes for most requests.
Technically, a poorly formed loop might DOS a child if the number of params
or headers is evilly large.
For instance, someone silly could write
my $params =
Hi there,
On Tue, 4 Feb 2003, Rob Lambden wrote:
I have written a request handler in Perl. I recently changed some code
in this to convert from using CGI within mod_perl to using Apache::Registry.
It's generally best to write handlers. If you have written a handler,
in general I think you
Rob Lambden wrote:
sub SetupPageArguments()
{
my ($DB, $nLoop, @Query, $Key, $Value);
$DB=shift;
@{$DB-{Page}-{'.parameters'}}=$DB-{ApacheReq}-param();
for($nLoop=0; $nLoop=$#{$DB-{Page}-{'.parameters'}}; $nLoop++)
{
Hi guys,
Thanks for your replies. Problem still not solved but I'll let
you know if I find an answer.
George.
Lee Goddard wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
Hi Stas,
On Tuesday, February 4, 2003 at 2:47:43 AM, you wrote:
SB Lee Goddard wrote:
SB [...]
I don't
(Originally posted as Apache::Registry incompatible with CGI? by mistake
- sorry !)
Hi,
I have written a request handler in Perl. I recently changed some code
in this to convert
from using CGI within mod_perl to using Apache::Request. The old code
was ...
$DB-{ApacheReq} = shift;
:
Perrin Hawkins wrote:
What's the purpose of that loop?
I am setting up an array in $DB-{Page}-{'.parameters'}[...] with each
entry
being the name of a parameter sent by the client. I am then setting up
an array
for each of these parameters in $DB-{Page}-{ParameterName}[...] with
one value
for
Lee Goddard wrote:
I don't know: you're doing this:
print Content-type: text/plain\n\n;
print Hello World\n;
Does it (probably not) make any difference if
you do a full CRLF, as perldoc perlop:
For example, most networking protocols expect
and prefer a CR+LF (\015\012 or \cM\cJ) for
John Eisenschmidt wrote:
OpenBSD 3.2
Perl 5.6.1
I'm trying to build MP 1.99_08 for Apache 2.0.44, and I'm not quite
sure where I'm messing up. Apache built fine, building the config for
MP went fine:
jweisen@kaitain$ sudo perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2
MP_INST_APACHE2=1
I downloaded Apache::Request from CPAN and I have version 0.31. My C
compiler is gcc 2.96
aiya. libapreq 0.31 is the one that likes to append whatever it is that
one just uploaded to it to its heap until it starves your machine of memory,
if i recall correctly. it was fixed in 0.31_03 i believe
Apache/1.3.26 + mod_perl/1.27
I've noticed that Apache alone appears to differ from one of my modules
running under mod_perl in its handling of trailing slashes. I'm wondering if
this is expected behavior and, if so, why? (Maybe this is obvious...)
For example: the file news.html exists in
kris nelson wrote:
Apache/1.3.26 + mod_perl/1.27
I've noticed that Apache alone appears to differ from one of my modules
running under mod_perl in its handling of trailing slashes. I'm wondering if
this is expected behavior and, if so, why? (Maybe this is obvious...)
For example: the file
kris == kris nelson [EMAIL PROTECTED] writes:
kris I've noticed that Apache alone appears to differ from one of my
kris modules running under mod_perl in its handling of trailing
kris slashes. I'm wondering if this is expected behavior and, if so,
kris why? (Maybe this is obvious...)
Yes,
Hello everyone,
I am currently running a web server using Perl CGI for
all my web sites and have been attracted to mod_perl
for the performance advantages - particularly not
having to start a new perl interpreter for each
request. I have tried using Apache::Register and
Apache::PerlRun but am
this is probably evil, and apologies to those who have seen suspiciously
familiar code before, but is this possible?
package MyPrefix::Apache::Registry;
use strict;
BEGIN {
use Apache::Registry();
}
sub handler {
delete $INC{'Site.pm'};
# mess with @INC
require Site;
David Dick wrote:
this is probably evil, and apologies to those who have seen suspiciously
familiar code before, but is this possible?
package MyPrefix::Apache::Registry;
use strict;
BEGIN {
use Apache::Registry();
}
sub handler {
delete $INC{'Site.pm'};
# mess with @INC
Pinunki wrote:
[...]
I have tried using Apache::Register and
Apache::PerlRun but am having problems due to the fact
that each web site refers to their own copy of my
module called Site.pm (to contain functions, global
variables etc). The problem is that the my scripts get
confused and use
David Dick wrote:
alrightly, back again. The problem is that Apache::Registry will return
a 206, which will trigger the error message. In case there is anyone
out there as daft as me :), the crude delegation-type module below can
solve this problem. Maniacs who see a need to return 204's,
If I'm correct both Apache::PerlRun and Apache::Registry will have
problems in certain situations if we agree that ModPerl::Registry has
the correct logic for handling the execution status. If you can tell
otherwise please give me a test script that doesn't work under
ModPerl::Registry.
But in
23 matches
Mail list logo
