httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51103] mod_reqtimeout does not drop connection and return 408
Date Mon, 25 Apr 2011 18:57:22 GMT

Stefan Fritsch <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Stefan Fritsch <> 2011-04-25 14:57:19 EDT ---
(In reply to comment #3)
> I have attached a Wireshark dump to the bug report. Let me know if this is
> what you expected, I'm actually new to Wireshark.

Thanks, that was what I wanted.

> We have mod_status listening on /server-status and it's responding correctly
> when invoking with a browser.
> Apache is now returning a 400 code, similar to the slow-headers attack. We did
> tweak a few settings (disabled ModSecurity, turned off ExtendedStatus) so it
> might have had that effect. I will investigate further.

But as you say, it does not show a 200 result code. I will mark this as invalid
because for the other issues, there have already been different PRs. If you can
reproduce the code 200 sent despite of a timeout issue, please change the
status from INVALID to REOPENED.

> > This happens in various situations and is fixed in trunk. The fixes should
> > probably be backported to 2.2.x. The relevant commits are r820760 r919323
> > r937858 r938265
> This is good to know. Do you have any idea when these changes will be
> backported or when 2.3 will be released?

I have now proposed them for the next 2.2.x release.

2.4 is hopefully due in 1-2 months.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message