Re: bug in mod_perl-1.24 & request->args & request->content

2001-01-25 Thread Doug MacEachern
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

bug in mod_perl-1.24 & request->args & request->content

2001-01-22 Thread Marc Lehmann
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; However, this might return an odd number of values, for e

Re: possible bug in mod_perl 1.24_01

2000-12-19 Thread Doug MacEachern
On Wed, 18 Oct 2000, Michael J Schout wrote: > I have had an application working under apache 1.3.12/mod_perl 1.24 for several > months now with no problems. > > I am currently trying to make the jump to apache 1.3.14/mod_perl 1.24_01 (since > mod_perl 1.24 will not easily build agains 1.3.14).

RE: possible bug in mod_perl 1.24_01

2000-10-19 Thread Geoffrey Young
> -Original Message- > From: Michael J Schout [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 18, 2000 2:54 PM > To: [EMAIL PROTECTED] > Subject: Re: possible bug in mod_perl 1.24_01 > > > I should also have mentioned: > > I am using perl 5.6.0

Re: possible bug in mod_perl 1.24_01

2000-10-18 Thread Michael J Schout
I should also have mentioned: I am using perl 5.6.0, Linux 2.2.x I used the same perl / os for both apache1.3.12/mod_perl 1.24, and apache 1.3.14/mod_perl 1.24_01. Mike

possible bug in mod_perl 1.24_01

2000-10-18 Thread Michael J Schout
I have had an application working under apache 1.3.12/mod_perl 1.24 for several months now with no problems. I am currently trying to make the jump to apache 1.3.14/mod_perl 1.24_01 (since mod_perl 1.24 will not easily build agains 1.3.14). When I do this, and then try to start apache, it goes i

Re: Bug in mod_perl

2000-10-13 Thread Doug MacEachern
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

Re: Bug in mod_perl

2000-10-09 Thread Ken Williams
[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

Re: Bug in mod_perl

2000-10-09 Thread Greg Williams
>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

Re: Bug in mod_perl

2000-10-09 Thread Tom Brown
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

Bug in mod_perl

2000-10-09 Thread Dave Rolsky
Try the following handler: package Foo; use Apache::Request; sub handler { my $r = shift; my (@vars) = ( 'abc', "abc\0def", "def" ); $r->send_http_header; $r->print("$_\n") foreach @vars; } 1; I'm using mod_perl 1.24/Apache 1.3.12/Perl 5.00503 and find that I receive no ou

Re: Bug? in mod_perl when POST request yields REDIRECT

2000-09-27 Thread Doug MacEachern
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

Re: Bug? in mod_perl when POST request yields REDIRECT

2000-09-27 Thread Doug MacEachern
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

Bug? in mod_perl when POST request yields REDIRECT

2000-09-06 Thread Reif Peter
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, 302, ...) with a Location: header, no data is

Fwd: apache_1.3.12 / mod_perl-1.22 ... Bug in mod_perl 1.22 on certain platform ?

2000-04-14 Thread Frédéric Schwien
Hi Following to my last email, I tried to build apache_1.3.12 with mod_perl-1.21. And it worked well with the same makepl_args.mod_perl file . So does that mean that there is a bug in mod_perl-1.22 ? Or That my conf file had wrong arguments in it, even if I could build it on an other server

Re: Bug in mod_perl makefile?

2000-02-03 Thread Stas Bekman
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] > >

Bug in mod_perl makefile?

2000-02-03 Thread Martin A. Langhoff
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] and was compiling modperl/perl with: #perl Makefile.PL APACH

Re: Fix for Redhat(?) bug in mod_perl install

1999-12-14 Thread Doug MacEachern
On Sat, 4 Dec 1999, Autarch wrote: > I don't remember if this has been discussed before but anyway. If you're > running Redhat 6.0 (and maybe 6.1?) there may be some weirdness when you > try to install modperl. Basically, when you go to run make on apache, it > gives it some -L or -I flags that

Re: Fix for Redhat(?) bug in mod_perl install

1999-12-05 Thread Remi Fasol
> On Sat, 4 Dec 1999, Autarch wrote: > > > I don't remember if this has been discussed before > but anyway. If you're > > running Redhat 6.0 (and maybe 6.1?) > > Just this moment installed a RH-6.1 system. It did > not exhibit this > problem. fwiw, my install of RH6.0 didn't have this proble

Re: Fix for Redhat(?) bug in mod_perl install

1999-12-05 Thread Tom Mornini
On Sat, 4 Dec 1999, Autarch wrote: > I don't remember if this has been discussed before but anyway. If you're > running Redhat 6.0 (and maybe 6.1?) Just this moment installed a RH-6.1 system. It did not exhibit this problem. > there may be some weirdness when you > try to install modperl. Bas

Re: Fix for Redhat(?) bug in mod_perl install

1999-12-04 Thread Stas Bekman
> I don't remember if this has been discussed before but anyway. If you're > running Redhat 6.0 (and maybe 6.1?) there may be some weirdness when you > try to install modperl. Basically, when you go to run make on apache, it > gives it some -L or -I flags that include libgdbm, because your Perl

Fix for Redhat(?) bug in mod_perl install

1999-12-04 Thread Autarch
I don't remember if this has been discussed before but anyway. If you're running Redhat 6.0 (and maybe 6.1?) there may be some weirdness when you try to install modperl. Basically, when you go to run make on apache, it gives it some -L or -I flags that include libgdbm, because your Perl was comp