From 9f59f39bafdc11a530e0cbf7ea65b51113f058b0 Mon Sep 17 00:00:00 2001
From: Eric Covener ftp:
or nntp
:
AcceptFilter nntp none
The default protocol names are https
for port 443
+ and http
for all other ports. To specify another protocol
+ is being used with a listening port, add the protocol
+ argument to the Listen
+ directive.
The default values on FreeBSD are:
This directive specifies the number of bytes from 0
(meaning unlimited) to 2147483647 (2GB) that are allowed in a
- request body.
AcceptFilter http httpready
@@ -2026,7 +2032,8 @@ from the client
The LimitRequestBody
directive allows
the user to set a limit on the allowed size of an HTTP request
@@ -2053,6 +2060,10 @@ from the client
LimitRequestBody 102400
For a full description of how this directive is interpreted by
+ proxy requests, see the mod_proxy
documentation.
This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a - request body.
+ request body. See the note below for the limited applicability + to proxy requests.The For a full description of how this directive is interpreted by
+ proxy requests, see the
proxy-sendchunked
minimizes resource usage by using
chunked encoding.
+ Under some circumstances, the server must spool request bodies + to disk to satisfy the requested handling of request bodies. For + example, this spooling will occur if the original body was sent with + chunked encoding (and and is large), but the administrator has + asked for backend requests to be sent with Content-Length or as HTTP/1.0. + This spooling can also occur if the request body already has a + Content-Length header, but the server is configured to filter incoming + request bodies.
+ +LimitRequestBody
only applies to
+ request bodies that the server will spool to disk
proxy-sendchunked
minimizes resource usage by using
chunked encoding.
+ Under some circumstances, the server must spool request bodies + to disk to satisfy the requested handling of request bodies. For + example, this spooling will occur if the original body was sent with + chunked encoding (and and is large), but the administrator has + asked for backend requests to be sent with Content-Length or as HTTP/1.0. + This spooling can also occur if the request body already has a + Content-Length header, but the server is configured to filter incoming + request bodies.
+ +