On Tue, 16 Jan 2001, Darren Stuart Embry wrote:
> On 2001-01-15, Ask Bjoern Hansen <[EMAIL PROTECTED]> wrote:
>
> > > When I do neither, i.e., leave the POST request as is and use
> > > the standard redirect mechanism, the browser hangs and the
> > > server actually does not send the redirect until I hit the Stop
> > > button (I'm using ngrep to determine this). This also happens
> > > if I use the $r->print($header) method and still return
> > > REDIRECT.
>
> > Try adding
> >
> > $r->method('GET');
> > $r->headers_in->unset('Content-length');
> >
> > to your code before doing the return REDIRECT.
>
> Ask Bjoern, I privately replied to you on this as well.
>
> I should have been more clear and said I was doing exactly this,
> as per [1], when I mentioned I was converting POST requests to
> GET requests.
>
> This is so that I could get redirects to work in response to a
> urlencoded POST request using the standard redirection technique
> of setting the Location header and mime type and returning
> REDIRECT instead of manually constructing and $r->print()ing a
> header.
>
> In any case, [1] does me no good with multipart/form-data which
> is what I was asking about in the first place.
you need 1.24_01 which contains this fix:
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() on
error or redirect after all data has been read
