[...]
Basically we are losing data sent to a mod_perl program. We request the
page "page.fxml?name=al&adress=sweden&problem=huge". When our program
receives this request it will only be "page.fxml" without any of the
arguments sent.
[...]
I haven't followed the original thread, so I apologize i
Hello.
I have posted a note here before, and want to thank those that took time
to try to solve this strange problem, but unfortunately none of the
suggestions have helped us so far, except for helping us ruling out things
that could have been incorrect.
Now I have received some more information
Hi Hakan,
CGI::Minimal has a "truncate" function that picks up invalid CGI
data ... this may help.
Nigel
> On Wed, 2 Oct 2002, Wes Cravens wrote:
>
> > On 02 Oct 2002 15:23 GMT I wrote:
> >
> > >
> > > Hi!
> > >
> > > We're developing a perl module for apache/mod_perl, but have enco
On Wed, 2 Oct 2002, Wes Cravens wrote:
> On 02 Oct 2002 15:23 GMT I wrote:
>
> >
> > Hi!
> >
> > We're developing a perl module for apache/mod_perl, but have encountered a
> > really strange problem.
> >
> > After 'a while' we seem to lose the data sent to the apache-server, at
> > least it never
On 02 Oct 2002 15:23 GMT you wrote:
>
> Hi!
>
> We're developing a perl module for apache/mod_perl, but have encountered a
> really strange problem.
>
> After 'a while' we seem to lose the data sent to the apache-server, at
> least it never reaches our module.
> Recently we switched from us
On Monday, 2002-09-23 at 11:11:02 -0400, darren chamberlain wrote:
> * Michael McLagan <[EMAIL PROTECTED]> [2002-09-21 11:45]:
> > There is a bug in Apache::Cookie. It doesn't handle a cookie with
> > zero bytes in it!
> This is because Apache::Cookie is implemented in C, and C uses NULL as
> th
* Michael McLagan <[EMAIL PROTECTED]> [2002-09-21 11:45]:
> There is a bug in Apache::Cookie. It doesn't handle a cookie with
> zero bytes in it!
This is because Apache::Cookie is implemented in C, and C uses NULL as
the end of string terminator.
This is probably something that needs to be done
Once upon a time, I wrote:
> There is a bug in Apache::Cookie. It doesn't handle a cookie
> with zero bytes in it!
A clarification, it's not a zero length cookie that is mishandled, it's a
cookie with an embedded NUL (zero) character.
Michael
D.Kreft wrote:
...
> I am greeted with Netcape's "Document contains no data" error dialog
> box, and a segfault notice in the error log:
>
>[Thu May 9 09:19:52 2002] [notice] child pid 25420 exit \
>signal Segmentation fault (11)
...
> Does anyone have any ideas about what's going wrong
On Mon, 15 Apr 2002, Stas Bekman wrote:
> >
> > Unfortunately, I don't have time for compiling and installing it..
> > I hope somebody on this list who has already installed version of recent perl
> > will test the problem..
>
> Confirmed as working with bleadperl (i.e the latest perl-5.7.3)
Vlad Harchev wrote:
>>> When using the following script under mod_perl, each httpd process crashes on
>>>the 2nd request to execute this script.
>>>
>>>#!/usr/bin/perl
>>>use strict; use POSIX qw(locale_h);
>>>setlocale(LC_ALL,'en_US.utf8');
>>>print "Expires: 1 Jan 1970\nContent-
On Sun, 14 Apr 2002, Stas Bekman wrote:
Hi,
> Vlad Harchev wrote:
> > Hi,
> >
> > When using the following script under mod_perl, each httpd process crashes on
> > the 2nd request to execute this script.
> >
> > #!/usr/bin/perl
> > use strict; use POSIX qw(locale_h);
> > set
Vlad Harchev wrote:
> Hi,
>
> When using the following script under mod_perl, each httpd process crashes on
> the 2nd request to execute this script.
>
> #!/usr/bin/perl
> use strict; use POSIX qw(locale_h);
> setlocale(LC_ALL,'en_US.utf8');
> print "Expires: 1 Jan 1970\nConte
On Fri, Feb 15, 2002 at 12:17:07PM -0800, Paul Lindner wrote:
> On Fri, Feb 15, 2002 at 11:44:03AM -0600, Fister, Mark wrote:
> >
> > > Dear mod_perl experts:
> > >
> > > Collectively, we've been at this for more than two weeks and have
searched
> > > various mod_perl archives, all to no avail.
> > The only other way I can think of to solve this is to send my module
list
> > to this audience. Please find it, attached, with home-grown modules
> > deleted.
>
> Have you tried debugging the old-fashioned way, i.e. remove things until
it
> works? That's your best bet. I suspect you will f
On Fri, Feb 15, 2002 at 11:44:03AM -0600, Fister, Mark wrote:
>
> > Dear mod_perl experts:
> >
> > Collectively, we've been at this for more than two weeks and have searched
> > various mod_perl archives, all to no avail.
> >
> > Symptom:
> > ===
> > SIGSEGV after fork(). Very reproducible
At 11:44 AM -0600 2/15/02, Fister, Mark wrote:
> > Dear mod_perl experts:
>>
>> Collectively, we've been at this for more than two weeks and have searched
>> various mod_perl archives, all to no avail.
>>
>> Symptom:
>> ===
>> SIGSEGV after fork(). Very reproducible. Memory corruption gets m
> The only other way I can think of to solve this is to send my module list
> to this audience. Please find it, attached, with home-grown modules
> deleted.
Have you tried debugging the old-fashioned way, i.e. remove things until it
works? That's your best bet. I suspect you will find that you
On Wed, 1 Aug 2001 13:12:44 +0200
"Issac Goldstand" <[EMAIL PROTECTED]> wrote:
> > based on the earlier discussion about detecting https :)
>
> That will take care of standard http/https, but what if we have a custom
> client connecting on weird ports _without_ putting the port in the URL?
> Wou
Thanks for that. However, I've already seen this. The problem is that I'm
requesting pages at:
http://my.server.com/perl/blah.pl
and also
https://my.server.com/perl/blah.pl
Now these should be different scripts, and Apache is set up with a
completely different document and perl root for the ht
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 01, 2001 10:50 AM
> To: Geoffrey Young
> Cc: Chris Rodgers; [EMAIL PROTECTED]
> Subject: RE: Bug??
>
[snip]
> >
> > of course, that won't work wi
On Wed, 1 Aug 2001, Geoffrey Young wrote:
>
>
> > -Original Message-
> > From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 31, 2001 11:17 PM
> > To: Chris Rodgers
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: Bug??
> >
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 31, 2001 11:17 PM
> To: Chris Rodgers
> Cc: [EMAIL PROTECTED]
> Subject: Re: Bug??
>
>
> On Tue, 31 Jul 2001, Chris Rodgers wrote:
>
> > Thanks for that.
- Original Message -
From: "Stas Bekman" <[EMAIL PROTECTED]>
To: "Chris Rodgers" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 05:16
Subject: Re: Bug??
> On Tue, 31 Jul 2001, Chris Rodgers wrote:
>
> > Tha
On Tue, 31 Jul 2001, Chris Rodgers wrote:
> Thanks for that. However, I've already seen this. The problem is that I'm
> requesting pages at:
>
> http://my.server.com/perl/blah.pl
>
> and also
>
> https://my.server.com/perl/blah.pl
>
> Now these should be different scripts, and Apache is set up wi
On Tue, 31 Jul 2001, Chris Rodgers wrote:
> Hi,
>
> I'm running Apache with mod_perl and mod_ssl. ("Apache/1.3.20 (Unix)
> mod_perl/1.25 mod_ssl/2.8.4 OpenSSL/0.9.5a" to be precise.)
>
> I am listening on both port 80 (HTTP) and port 443 (HTTPS) and serving perl
> scripts. There are two separate
> Can't all these modules (your scripts,
The environment leak in my test case was just to make my point clear,
not a programmatic example of course
> mod_ssl, etc) just use the request object and/or Apache notes to
> communicate? That's exactly what they're there for!
I get it now: there
On Wed, Jul 18, 2001 at 11:41:01AM -0400, Geoffrey Young wrote:
> well, in mod_cgi land it's not that easy to access r->notes, right? but
> there is no reason that mod_ssl and friends couldn't set both for those of
> us who can...
*and* to (please!) have a way to turn off the environment crap in
> -Original Message-
> From: Roger Espel Llima [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 11:35 AM
> To: [EMAIL PROTECTED]
> Cc: Dominique Quatravaux
> Subject: Re: [BUG] $r->subprocess_env() leaking to %ENV
>
>
[snip]
> Can
Dominique Quatravaux <[EMAIL PROTECTED]> wrote:
> I found the following behaviour in mod_perl, which is clearly
> unexpected: I use an Apache that can serve both mod_perl and PHP
> pages. I run it -X ; first I request the URI for this scriptlet
> (under mod_perl's Apache::Registry):
>
> #!/usr/bi
FYI
http://forum.swarthmore.edu/epigone/modperl/quajugrar/DDC7EF25B9D6D311A2
[EMAIL PROTECTED]
-Original Message-
From: Dominique Quatravaux [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 2:24 PM
To: [EMAIL PROTECTED]
Subject: [BUG] $r->subprocess_env() leaking to %ENV
He
On Fri, Jul 06, 2001 at 01:50:57PM -0700, Doug MacEachern wrote:
> On Wed, 23 May 2001, Julian Gilbey wrote:
>
> > On Mon, May 21, 2001 at 06:36:54PM +0100, Julian Gilbey wrote:
> > > We've just upgraded a SunOS machine from Apache 1.3.9 + mod_perl 1.21
> > > (dynamically linked) to Apache 1.3.19
On Wed, 23 May 2001, Julian Gilbey wrote:
> On Mon, May 21, 2001 at 06:36:54PM +0100, Julian Gilbey wrote:
> > We've just upgraded a SunOS machine from Apache 1.3.9 + mod_perl 1.21
> > (dynamically linked) to Apache 1.3.19 + mod_perl 1.25 (statically
> > linked). I have a CGI/Perl script, handle
On Wed, 23 May 2001, Julian Gilbey wrote:
> Right, here's a patch. This line of code was erroneously removed some
> time between version 1.21 and 1.25 of mod_perl.
see Changes:
"fix bug where Apache::send_http_header was resetting r->status = 200
thanks to brian d foy for the spot"
the proble
> Version: Apache/1.3.12 (Unix) mod_perl/1.24
> What: PerlAuthenHandler returns headers without WWW-Authenticate field
> Work-around: set with $r->err_header_out
It looks like you haven't fully read the book/docs/manpages/samples for auth
handling.
*All* of the code for Basic auth (i.e. browser b
I noticed this behavior as well.
> I've noticed an inconcistency between PerlModule and use() (and
> PerlRequire and require()).
> "Joseph" == Joseph Crotty <[EMAIL PROTECTED]> writes:
Joseph> Is there any sort of mod_perl bug repository??
You mean where the bugs live? I think that's called "the source code".
:-)
"bug reports" would be a different matter. I presume Doug is keeping
track of those.
--
Randal L. Sc
On Thu, 18 Jan 2001, Paul Walmsley wrote:
>
> (In the post below, 'STDIN', 'STDOUT', and 'STDERR' refer to Perl
> filehandles, while 'stdin', 'stdout', and 'stderr' refer to Perl file
> descriptors.)
>
> During migration of a web application server from Perl 5.00503 to Perl
> 5.6, we discovered
On Mon, 22 Jan 2001, Marc Lehmann wrote:
> Apache.pm documents two methods "args" and "content" that should return
> argument => value pairs (when called appropriately). In fact, args is
> implemented as:
>
> return map { Apache::unescape_url_info($_) } split /[=&;]/, $string, -1;
>
> H
On Fri, 12 Jan 2001, Richard L. Goerwitz wrote:
> The mod_perl-1.24_01 ./src/modules/perl/Server.xs file is using a
> short int, which leads to ports between 32768 and 65535 (inclusive)
> turning up in Perl as negative numbers -
thanks, this should fix the problem..
Index: src/modules/perl/Serv
The mod_perl-1.24_01 ./src/modules/perl/Server.xs file is using a
short int, which leads to ports between 32768 and 65535 (inclusive)
turning up in Perl as negative numbers -
short
port(server, ...)
Apache::Server server
CODE:
RETVAL = server->port;
if(items > 1)
se
On Fri, Dec 08, 2000 at 07:23:08PM +0400, BeerBong wrote:
> Hello!
>
> I tried to migrate to Apache 1.3.14 from 1.3.12 ...
> Heh.
> After recompiling apache and starting the server with the same config get
> 400 Bad request on any request to mod_perl back-end server. Static html and
> images are
On Mon, 9 Oct 2000, Dave Rolsky wrote:
> I'm using mod_perl 1.24/Apache 1.3.12/Perl 5.00503 and find that I receive
> no output after the \0. Is this a mod_perl or Apache bug? Or is it a
> client bug (using Netscape 4.75) or is it the expected behavior.
looks ok to me:
% telnet localhost 852
[EMAIL PROTECTED] (Greg Williams) wrote:
>>I'm using mod_perl 1.24/Apache 1.3.12/Perl 5.00503 and find that I receive
>>no output after the \0. Is this a mod_perl or Apache bug? Or is it a
>>client bug (using Netscape 4.75) or is it the expected behavior.
>
>It would be expected, I'd assume. pe
>I'm using mod_perl 1.24/Apache 1.3.12/Perl 5.00503 and find that I receive
>no output after the \0. Is this a mod_perl or Apache bug? Or is it a
>client bug (using Netscape 4.75) or is it the expected behavior.
It would be expected, I'd assume. perl5-porters discussed this back
in January wh
Interesting, the Mason bug report I just filed is obviously mis-filed.
Apache::Registry scripts suffer the same behaviour.
On Mon, 9 Oct 2000, Dave Rolsky wrote:
> Try the following handler:
>
> package Foo;
>
> use Apache::Request;
>
> sub handler
> {
> my $r = shift;
>
> my (@va
[Please keep the CC: to bugs.debian.org]
On Mon, Oct 09, 2000 at 10:59:29PM +0200, [EMAIL PROTECTED] wrote:
> Package: apache-perl
> Version: 1.3.9-13.1-1.21.2309-1
> Severity: normal
>
> I've tried to create a package `libapache-request-perl'
> (Module Apache::Request). (Such a package does
take 2 on that patch, this one adds a check so ap_setup_client_block() is
only called once. with this part of the fix you can call $r->content
multiple times without hanging:
my $data = $r->content;
$data = $r->content;
however, any calls to $r->content after the first will return undef.
(unles
On Wed, 6 Sep 2000, Reif Peter wrote:
> I am using a self written mod_perl module that does proxy requests. It acts
> as content handler and fetches the requestet documents via LWP::UserAgent.
> The program works fine but when the request is a POST request and the
> response is a redirection (301
My personal feeling about XMLSubs is that it should
take the code out of the HTML to some perl library.
So to use an XMLSub with perl expression as the args
to the tag though possible is not what I would recommend.
To do what you want below, I would recommend having all
of the logic in the perl
ED]'
Cc: 'Joshua Chamas'
Subject: RE: Bug in Apache::ASP XMLSubs when an argument includes
'>'-characte rs?
Joshua Chamas wrote:
>
> I think > is just about the only thing that you can't use as
> a character in the attributes for an XMLSubs and that'
Joshua Chamas wrote:
>
> I think > is just about the only thing that you can't use as
> a character in the attributes for an XMLSubs and that's because
> it gets parsed with an aggressive ( or stupid ;) regexp like:
>
> $$data =~ s|\<\s*($self->{xml_subs_match})([^\>]*)/\>
Pity!
I would
Henrik Tougaard wrote:
>
> > XML attributes can't contain "<" or "&" characters, or the
> > same quote that
> > they are surrounded by. The following are the encodings you can use
> > (and XMLSubsMatch needs to unravel):
> >
> > < => "<"
> > > => ">"
> > & => "&"
> > " => """
> > '
On Tue, 15 Aug 2000, Henrik Tougaard wrote:
> > XML attributes can't contain "<" or "&" characters, or the
> > same quote that
> > they are surrounded by. The following are the encodings you can use
> > (and XMLSubsMatch needs to unravel):
> >
> > < => "<"
> > > => ">"
> > & => "&"
> >
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> On Fri, 11 Aug 2000, Henrik Tougaard wrote:
> > With this simple .asp page I get an error:
> >
> >
> > [My XMLSubMatch is set to Fiks:\w+ - the name of the
> subroutine doesn't
> > matter]
> >
> > It seems as if the '>' in the '' argumen
On Fri, 11 Aug 2000, Henrik Tougaard wrote:
> I have been trying to test the limits of the nice new XMLSub feature in
> Apache::ASP, and seem to have discovered a bug.
>
> With this simple .asp page I get an error:
>
>
> [My XMLSubMatch is set to Fiks:\w+ - the name of the subroutine doe
On Tue, 11 Apr 2000, Ardo van Rangelrooij wrote:
Hi!
> Steve Dunham (thanks!!!)provided a patch which should take care of
> this problem. I've made a package available as
>
> http://master.debian.org/~ardo/libxml-parser-perl_2.27-3_i386.deb
>
> Please try it out and let me know what's up.
On Tue, 11 Apr 2000, Ardo van Rangelrooij wrote:
> Hi!
Hi,
> Steve Dunham (thanks!!!)provided a patch which should take care of
> this problem. I've made a package available as
>
> http://master.debian.org/~ardo/libxml-parser-perl_2.27-3_i386.deb
>
> Please try it out and let me know what'
Hi!
Steve Dunham (thanks!!!)provided a patch which should take care of
this problem. I've made a package available as
http://master.debian.org/~ardo/libxml-parser-perl_2.27-3_i386.deb
Please try it out and let me know what's up. If no problems occur
I'll upload it to master officially.
I'l
reassign 61231 libxml-parser-perl
thanks
And sure enough, the man is right. This is not mod_perl's problem.
When I disable RULE_EXPAT, apache ceases crashing.
On Tue, Apr 04, 2000 at 02:49:36PM -0700, Doug MacEachern wrote:
> On Tue, 4 Apr 2000, Daniel Jacobowitz wrote:
>
> > [mod_perl peopl
On Tue, 4 Apr 2000, Daniel Jacobowitz wrote:
> [mod_perl people - any comment? Please keep the Cc: list to the Debian
> bug tracking system.]
> > When using the XML::Parser::Expat under mod_perl, this causes segmentation
> > faults (quite random?) in the child-processes of httpd.
> > The error
Something, presumably XML::Parser::Expat, is corrupting malloc's and
perl's data structures randomly. Running under MALLOC_CHECK_=2 has a
high probability of showing this. It also occasionally cores in
Perl_sv_upgrade - the SV is hopelessly mangled:
(gdb) p *sv
$17 = {sv_any = 0x83e58955, sv_re
[mod_perl people - any comment? Please keep the Cc: list to the Debian
bug tracking system.]
On Tue, Mar 28, 2000 at 12:50:45PM +0200, [EMAIL PROTECTED] wrote:
> Package: libapache-mod-perl
> Version: 1.21.2309-1
> Severity: Important
>
> When using the XML::Parser::Expat under mod_perl, th
On Thu, 3 Feb 2000, Martin A. Langhoff wrote:
> Hi,
>
> I've just got my apache/modperl setup to work. This little nastie
> took me 2 days to find.
>
> In my /usr/src directory, I had:
> - apache_1.3.3 [dir]
> - apache_1.3.9 [dir]
> - mod_perl-1.21 [dir]
>
>
On Fri, Nov 19, 1999 at 10:10:07AM -0800, Jeffrey Baker wrote:
>
> if (defined @foo_in) {
Generally using defined() on aggregates is a bad idea.
Tim.
On Fri, 19 Nov 1999, Jeffrey Baker wrote:
> I don't care whether Perl has allocate memory or not. All I care about
> is whether or not there are any defined entries in the list, which I
> think is most clearly expressed as 'if (defined $list[0])'. What is
> more clear than that? 'if (@list)' c
Randal L. Schwartz wrote:
> "if (@foo) {...}" is *idiomatic* Perl for "are there any elements in
> @foo, and if so, do this". If you don't understand the idioms, please
> choose a more familiar language. :)
Don't you think this is a rather nasty response, smiley notwithstanding? Normally I
enj
Not really, just create a file called makepl_args.mod_perl such as:
--cut here--
# for Apache 1.3.6 and mod_perl 1.19+
# PERL_POST_READ_REQUEST=1 PERL_TIE_TABLES=1 PERL_SSI=1
# PERL_STACKED_HANDLERS=1 USE_APACI=1
EVERYTHING=1 USE_DSO=1 USE_APACI=1
APACI_ARGS=--with-layout=../apache-bsdi.layout:bs
Tom Lancaster wrote:
>
> Hi all,
> I've searched the list for this, but to no avail.
> I'm using 1.3.9 / 1.21 / latest Apache::DBI, Embperl 1.2b7, Perl 5.00503
>
> Anywho, this the problem:
> When I enable Apache::DBI in httpd.conf, the server simply won't start.
> No error log messages, no noth
On Fri, 19 Nov 1999, Matt Sergeant wrote:
> httpd -X
good production solution.
> "Jeffrey" == Jeffrey Baker <[EMAIL PROTECTED]> writes:
Jeffrey> Yeah. I guess the reason I do the latter is b/c I want the code to
Jeffrey> reflect what I am actually trying to test. I don't really want to test
Jeffrey> the trueness of @foo, I want to test for it's existence. But in perl
Ken Williams wrote:
> Are you sure? I'm still not sure you understand about defined(@list). It
> actually tests whether Perl has allocated memory for the structure, not whether
> the structure has ever been used or anything like that. And even the present
> behavior may change without notice.
[EMAIL PROTECTED] (Jeffrey Baker) wrote:
>Cliff Rayman wrote:
>>
>> `perldoc -f defined` yields a couple of sentences:
>>
>> You may also use C to check whether a subroutine exists, by
>> saying C without parentheses. On the other hand, use
>> of C upon aggregates (hashes and arrays) is not gua
On Fri, 19 Nov 1999, Jeffrey Baker wrote:
> 1) Visit /yoururl
> 2) Visit /yoururl?foo=bar&foo=baz
> 3) Visit /yoururl as many times as you have Apache child processes
httpd -X
--
Details: FastNet Software Ltd - XML, Perl, Databases.
Tagline: High Performance Web Solutions
Web Sites: http://co
Cliff Rayman wrote:
>
> `perldoc -f defined` yields a couple of sentences:
>
> You may also use C to check whether a subroutine exists, by
> saying C without parentheses. On the other hand, use
> of C upon aggregates (hashes and arrays) is not guaranteed to
> produce intuitive results, and shou
`perldoc -f defined` yields a couple of sentences:
You may also use C to check whether a subroutine exists, by
saying C without parentheses. On the other hand, use
of C upon aggregates (hashes and arrays) is not guaranteed to
produce intuitive results, and should probably be avoided.
why not us
I should have mentioned in this bug report that the problem only occurs
when you call $r->param in a list context. Everything is fine in a
scalar context. For that reason I suspect this little bit of code:
sub param {
my $self = shift;
my($name, $value) = @_;
my $tab = $self->parms;
77 matches
Mail list logo
