On 2021-05-19 11:57 +02, Matthias Pressfreund <[email protected]> wrote:
> While trying to figure out why the May 17 patch in my case does
> not behave as expected, I was adding some extra debug output to
> server_fcgi_read, server_fcgi_header and server_fcgi_writechunk
> and started a httpd debug session during which I was signing in
> and out of a WordPress site's admin interface. Both actions were
> delayed by 30 seconds which corresponds to the request timeout
> specified in the httpd configuration.
> Please find attached the session transcript and my additions to
Please indicate where you experience a 30 second delay.
You get a 302 Found with no body so it's not chunk encoded and a 200
which is still chunk encoded. The 302 Found transcript looks fine to me,
too. No idea what's going on. I also can't reproduce with a simple 302
cgi script.
> server_fcgi.c.
A diff would have been nice.
>
> The two places of importance are lines 314 and 2195 where the
Huh?
$ wc -l server_fcgi.c
793 server_fcgi.c
there is no line 2195
> patch forces fcgi.chunked to be 0 assuming there is no content
> because server_fcgi_header was called in the course of an
> FCGI_END_REQUEST. Is it possible this was not correct here as
> we actually did have content?
>
>
>
--
I'm not entirely sure you are real.
