dougm 02/05/27 11:39:03
Modified:src/modules/perl modperl_env.c
Log:
propagate scfg-SetEnv to %ENV
Revision ChangesPath
1.21 +26 -18modperl-2.0/src/modules/perl/modperl_env.c
Index: modperl_env.c
dougm 02/05/27 17:35:00
Modified:src/modules/perl modperl_env.c
Log:
untabify
Revision ChangesPath
1.23 +1 -1 modperl-2.0/src/modules/perl/modperl_env.c
Index: modperl_env.c
===
RCS
Dear List,
A modification to the sample Hello.pm
module yielded the odd result below. Note how the outgoing html which the
browser receiveshas been modified. The html content is important
(almost all html works correctly)and I have presented a simple
example.
Changing a single line in to
On Mon, 27 May 2002, Charles Frankel wrote:
Dear List,
A modification to the sample Hello.pm module yielded the odd result below.
Note how the outgoing html which the browser receives has been modified.
The html content is important (almost all html works correctly) and I have
presented a
maybe you can try a chmod 755 in the script...and check the perl path in first line
of the script...and set the directory permission to 777
-Original Message-
From: Ian D. Stewart [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 26, 2002 10:44 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL
On 2002.05.27 11:43 Lucas M. Saud wrote:
maybe you can try a chmod 755 in the script...and check the perl
path in first line of the script...and set the directory permission to
777
Tried all of those. Still no good.
I've downloaded the source for both Apache and mod_perl, and will be
Yeah, I'd be interested in seeing that. It sounds like it might have
parallels to a problem I'm having with inserting markup in html, and I'm
interested to see your approach.
Depending on what sort of quality you require, you might want to look at
the approach and the specific regexes which
On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart wrote:
On 2002.05.27 11:43 Lucas M. Saud wrote:
maybe you can try a chmod 755 in the script...and check the perl
path in first line of the script...and set the directory permission to
777
Tried all of those. Still no good.
Sounds to me like you're not setting your content-type correctly for some
reason. Have a look at the headers being sent out. It's either not
sending this header, or it's sending something the browser doesn't know
what to do with.
Andrew
On Sun, 26 May 2002, Ian D. Stewart wrote:
Date:
On 2002.05.27 12:57 Andrew McNaughton wrote:
Sounds to me like you're not setting your content-type correctly for
some
reason. Have a look at the headers being sent out. It's either not
sending this header, or it's sending something the browser doesn't
know
what to do with.
This is the
On 2002.05.27 12:59 Eric wrote:
On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart wrote:
On 2002.05.27 11:43 Lucas M. Saud wrote:
maybe you can try a chmod 755 in the script...and check the perl
path in first line of the script...and set the directory permission
to
777
On 2002.05.27 12:49 Randy Kobes wrote:
I didn't cc the list, as I've lost the original message,
but from what I remember, you had
Options ExecCGI
in a configuration. Does
Options +ExecCGI
make a difference? Also, as far as I remember, you had
PerlSendHeader On
Depending on
Dear Ian,
I think we may looking for the problem in the wrong place.
The fact that the browser offers to save something means that it is
receiving a response from the server, and that it is not interpreting said
response as HTML text.
You are not actually outputting any 'HTML', 'HEAD', or
Well, I haven't had any better luck with the debian package but I have
gotten Apache and mod_perl running by building from source.
Thanx for all the help,
Ian
On 2002.05.27 13:06 Ian D. Stewart wrote:
On 2002.05.27 12:59 Eric wrote:
On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart
Is it possible to reference the value of one Directive within another
Directive (e.g., PerlSetVar VariableName ${DocumentRoot}/subdir) ?
Thanx,
Ian
At 21:13 27.05.2002, Ian D. Stewart wrote:
Is it possible to reference the value of one Directive within another
Directive (e.g., PerlSetVar VariableName ${DocumentRoot}/subdir) ?
If you use Perl sections, yes.
Perl
$DocumentRoot = '/home/httpd/htdocs';
push @PerlSetVar, [ VariableName =
My guess is that some error message is terminating your headers before the
content-type is sent. stdout and stderr get buffered independently so the
stderr can come out of your script first, even if it's generated later in
your code.
* Set $|=1; as the first thing you do in your test script,
On Tue, 28 May 2002 04:52:48 +1200 (NZST), Andrew McNaughton wrote:
[snip]
i'm writting a module to highlighting of Perl syntactical
structures, but the current code is very slow... :(
i need some help to implementing a method of back-tracking or one
way to revising a token that has already been
On Tue, 28 May 2002, Ron Savage wrote:
On Tue, 28 May 2002 04:52:48 +1200 (NZST), Andrew McNaughton wrote:
[snip]
That's not me below, I quoted Lucas M. Saud [EMAIL PROTECTED]:
i'm writting a module to highlighting of Perl syntactical
structures, but the current code is very slow... :(
On 2002.05.27 15:39 Per Einar Ellefsen wrote:
At 21:13 27.05.2002, Ian D. Stewart wrote:
Is it possible to reference the value of one Directive within
another Directive (e.g., PerlSetVar VariableName
${DocumentRoot}/subdir) ?
If you use Perl sections, yes.
Perl
$DocumentRoot =
On Thu, 23 May 2002, Joe Yates wrote:
I have
Apache/2.0.36
mod_perl/1.99_02-dev
Perl/v5.7.3
and am using nmake.
Apache2 is installed (and working) in
C:\Apache2\bin
I built both perl and Apache from sources.
My makefile.pl command line is:
perl
21 matches
Mail list logo
