Are we able to disable the chunk transfer ? To send all in one shot ?
Geoffrey Young wrote:
Cyril SCETBON wrote:
Hi people,
I've got some problem with both cgi and modperl.
when I post something to /perl/test.pl which just print header and a
string I got some strange numbers. The post
Torsten Foertsch wrote:
On Wednesday 20 June 2007 09:45, Cyril SCETBON wrote:
Are we able to disable the chunk transfer ? To send all in one shot ?
Add a Content-Length output header and avoid output filters that can change
the content length.
Great. It works :-) when using $r
Torsten Foertsch wrote:
On Wednesday 20 June 2007 09:45, Cyril SCETBON wrote:
Are we able to disable the chunk transfer ? To send all in one shot ?
Add a Content-Length output header and avoid output filters that can change
the content length.
Great. It works :-) when using $r
Hi people,
I've got some problem with both cgi and modperl.
when I post something to /perl/test.pl which just print header and a
string I got some strange numbers. The post is done with a php script.
test.pl :
use strict;
use CGI qw/:standard/;
print header;
print(\ncoucou\n);
and below is
Perrin Harkins wrote:
On 6/15/07, Cyril SCETBON [EMAIL PROTECTED] wrote:
Is there any difference in using each syntax to signal a warning in the
error log of Apache ? Performance impact ?
Theoretically, the longer version is probably faster, but I doubt
you'll ever be able to measure
Hi people,
Is there any difference in using each syntax to signal a warning in the
error log of Apache ? Performance impact ?
Thanks
Jonathan Vanasco wrote:
On May 17, 2007, at 11:53 AM, Michael Peters wrote:
I would imagine the 2nd to be marginally faster. Perl doesn't have to
re-allocate memory for the array each time the sub is called, but it
does have
to re-initialize it. As long as the array's contents are constant
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Dec 27, 2006 at 04:56:50PM +0100, Cyril SCETBON wrote:
I'm using Modperl 2.0.2 with apache 2.0.55 and modperl is doing
something wrong with my string :
my $var=à présent protégé;
warn Dumper [$var];
my $var=à
I'm using Modperl 2.0.2 with apache 2.0.55 and modperl is doing
something wrong with my string :
my $var=à présent protégé;
warn Dumper [$var];
my $var=à présent protégé.$login;
warn Dumper [$var];
$VAR1 = [
'à présent protégé'
];
$VAR1 = [
\x{c3}\x{a0}
Cyril SCETBON wrote:
Hi people,
I get this error message int error.log when I try to access a perl
script which exists or not.
I've turned on trace messages in mod_perl and here is my error.log :
[Sun Oct 08 17:19:39 2006] [notice] Apache/2.0.55 (Ubuntu)
mod_ssl/2.0.55 OpenSSL/0.9.8a
- From: Cyril SCETBON [EMAIL PROTECTED]
To: modperl@perl.apache.org
Sent: Sunday, October 08, 2006 12:50 PM
Subject: child pid 28464 exit signal Segmentation fault (11)
Hi people,
I get this error message int error.log when I try to access a perl
script which exists or not.
I've turned on trace
11 matches
Mail list logo
