Differences between revisions 5 and 6
Revision 5 as of 2009-09-20 22:13:16
Size: 413
Editor: localhost
Comment: converted to 1.6 markup
Revision 6 as of 2012-10-13 18:14:41
Size: 737
Editor: TimBannister
Comment: Win32DisableAcceptEx isn't available in 2.4
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
This message is unique to MS Windows, and is generally caused by faulty firewall, antivirus, or networking software that interferes with the correct operation of the Windows networking APIs. This message is unique to Microsoft Windows, and is generally caused by faulty firewall, antivirus, VPN, or other networking software that interferes with the correct operation of the Windows networking APIs.
Line 6: Line 6:
You can work around this problem in Apache by using the {{{Win32DisableAcceptEx}}} directive to tell Apache to fall back to a more basic networking API. In Apache httpd 2.2, you can work around this problem in Apache by using the [[http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html#win32disableacceptex|Win32DisableAcceptEx]] directive to tell Apache to fall back to a more basic networking API.

In Apache httpd 2.4, use the [[http://httpd.apache.org/docs/2.4/mod/core.html#acceptfilter|AcceptFilter]] directive instead. Typically this will be:

`AcceptFilter http none`<<BR>>
`AcceptFilter https none`

AcceptEx Failed

This message is unique to Microsoft Windows, and is generally caused by faulty firewall, antivirus, VPN, or other networking software that interferes with the correct operation of the Windows networking APIs.

In Apache httpd 2.2, you can work around this problem in Apache by using the Win32DisableAcceptEx directive to tell Apache to fall back to a more basic networking API.

In Apache httpd 2.4, use the AcceptFilter directive instead. Typically this will be:

AcceptFilter http none
AcceptFilter https none

AcceptExFailed (last edited 2012-10-13 18:14:41 by TimBannister)