From: Doug MacEachern [EMAIL PROTECTED]
I've found that if I post to this PerlAccessHandler, I get no response:
this problem is fixed in 1.25, from Changes:
fix $r-read() so it will not block if all data has already been read
and so that Apache will not hang during ap_discard_request_body()
I've found that if I post to this PerlAccessHandler, I get no response:
#
package Apache::Redirect;
use strict;
use Apache::Constants qw(REDIRECT);
use CGI ();
sub handler {
my($r) = @_;
my $q = new CGI();
$r-header_out(Location =
On Wed, Jun 13, 2001 at 11:58:24AM -0400, David Young wrote:
I've found that if I post to this PerlAccessHandler, I get no response:
#
package Apache::Redirect;
use strict;
use Apache::Constants qw(REDIRECT);
use CGI ();
sub handler {
my($r) = @_;
my
From: David Young [EMAIL PROTECTED]
DY I've found that if I post to this PerlAccessHandler, I get no response:
DY $r-header_out(Location = http://www.modperl.com/;);
DY return REDIRECT;
- Are you actually wanting your orriginally POSTed data to make it to the
redirected location?
- Do
At 17:46 13.06.2001 +0100, you wrote:
Actually, it's apache not letting it redirect on a POST form. I don't know
why commenting out CGI makes any difference, but the HTTP RFC does say that
the behaviour is undefined, for 301/2 on anything other than GET, if you
think about it, this makes sense:
From: Rodney Broom [EMAIL PROTECTED]
From: David Young [EMAIL PROTECTED]
DY I've found that if I post to this PerlAccessHandler, I get no response:
DY $r-header_out(Location = http://www.modperl.com/;);
DY return REDIRECT;
- Are you actually wanting your orriginally POSTed data to
On Wed, 13 Jun 2001, David Young wrote:
I've found that if I post to this PerlAccessHandler, I get no response:
...
mod_perl/1.24
this problem is fixed in 1.25, from Changes:
fix $r-read() so it will not block if all data has already been read
and so that Apache will not hang during
