| Summary: | mpm_winnt fails without the Win32DisableAcceptEx directive | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Anders Steinlein <dinhelt> |
| Component: | mpm_winnt | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | dinhelt |
| Priority: | P2 | Keywords: | ErrorMessage |
| Version: | 2.0.55 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
patches welcome, going to close out this dup user config report |
I almost pulled my hair out having spent several hours trying to figure out why a vanilla installation simply would not work; requests seemed to loop ("Opening page..." in IE forever and ever) and no access log entry, error, notice or any indication of what was wrong were sent to the logs. Then I found the Win32DisableAcceptEx directive, which solved the problem. I've read the documentation for the directive, so I know the bug itself might be related to something external to Apache (although exiting virus scanners, firewalls etc on my computer didn't help). How widepread is this problem? If the bug itself is completely out of Apache's control, I suggest some enhancements which might help others encountering the same problem: - Sniff the behaviour of AcceptEx() upon starting Apache (if this is feasible), and log any potential problems found. (I did not encounter the error condition mentioned in the Win32DisableAcceptEx directive documentation - NO indication of a problem was given to me.) - Add the directive to the Windows-distributed httpd.conf in the WinNT MPM section (commented out by default, I would guess), making it clear to the user that there might be a potential problem lurking.