From: Jim Jagielski
The default values on Windows are:
-AcceptFilter http data -AcceptFilter https data+
AcceptFilter http connect +AcceptFilter https connect
Window's mpm_winnt interprets the AcceptFilter to toggle the AcceptEx()
- API, and does not support http protocol buffering. There are two values
- which utilize the Windows AcceptEx() API and will recycle network
- sockets between connections. data waits until data has
- been transmitted as documented above, and the initial data buffer and
- network endpoint addresses are all retrieved from the single AcceptEx()
- invocation. connect will use the AcceptEx() API, also
- retrieve the network endpoint addresses, but like none
- the connect option does not wait for the initial data
- transmission.
connect
+ will use the AcceptEx() API, also retrieve the network endpoint
+ addresses, but like none the connect option
+ does not wait for the initial data transmission.
On Windows, none uses accept() rather than AcceptEx()
and will not recycle sockets between connections. This is useful for
@@ -204,6 +199,22 @@ AcceptFilter https data
network providers such as vpn drivers, or spam, virus or spyware
filters.
data AcceptFilter (Windows)For versions 2.4.23 and prior, the Windows data accept
+ filter waited until data had been transmitted and the initial data
+ buffer and network endpoint addresses had been retrieved from the
+ single AcceptEx() invocation. This implementation was subject to a
+ denial of service attack and has been disabled.
Current releases of httpd default to the connect filter
+ on Windows, and will fall back to connect if
+ data is specified. Users of prior releases are encouraged
+ to add an explicit setting of connect for their
+ AcceptFilter, as shown above.
The default values on Windows are:
Window's mpm_winnt interprets the AcceptFilter to toggle the AcceptEx()
- API, and does not support http protocol buffering. There are two values
- which utilize the Windows AcceptEx() API and will recycle network
- sockets between connections. data waits until data has
- been transmitted as documented above, and the initial data buffer and
- network endpoint addresses are all retrieved from the single AcceptEx()
- invocation. connect will use the AcceptEx() API, also
- retrieve the network endpoint addresses, but like none
- the connect option does not wait for the initial data
- transmission.
connect
+ will use the AcceptEx() API, also retrieve the network endpoint
+ addresses, but like none the connect option
+ does not wait for the initial data transmission.
On Windows, none uses accept() rather than AcceptEx()
and will not recycle sockets between connections. This is useful for
@@ -106,6 +101,22 @@ AcceptFilter https data
network providers such as vpn drivers, or spam, virus or spyware
filters.
data AcceptFilter (Windows)For versions 2.4.23 and prior, the Windows data accept
+ filter waited until data had been transmitted and the initial data
+ buffer and network endpoint addresses had been retrieved from the
+ single AcceptEx() invocation. This implementation was subject to a
+ denial of service attack and has been disabled.
Current releases of httpd default to the connect filter
+ on Windows, and will fall back to connect if
+ data is specified. Users of prior releases are encouraged
+ to add an explicit setting of connect for their
+ AcceptFilter, as shown above.