COMMENT: bytes allow|deny acl acl...
DEFAULT_IF_NONE: 0 allow all
This option specifies the maximum size of a reply body in bytes.
It can be used to prevent users from downloading very large files,
such as MP3's and movies. When the reply headers are received,
the reply_body_max_size lines are processed, and the first line with
a result of "allow" is used as the maximum body size for this reply.
This size is checked twice. First when we get the reply headers,
we check the content-length value. If the content length value exists
and is larger than the allowed size, the request is denied and the
user receives an error message that says "the request or reply
is too large." If there is no content-length, and the reply
size exceeds this limit, the client's connection is just closed
and they will receive a partial reply.
WARNING: downstream caches probably can not detect a partial reply
if there is no content-length header, so they will cache
partial responses and give them out as hits. You should NOT
use this option if you have downstream caches.
If you set this parameter to zero (the default), there will be
no limit imposed.
DEFAULT: 4096 KB
Objects larger than this size will NOT be saved on disk. The
value is specified in kilobytes, and the default is 4MB. If
you wish to get a high BYTES hit ratio, you should probably
increase this (one 32 MB object hit counts for 3200 10KB
hits). If you wish to increase speed more than your want to
save bandwidth you should leave this low.
NOTE: if using the LFUDA replacement policy you should increase
this value to maximize the byte hit rate improvement of LFUDA!
See replacement_policy below for a discussion of this policy.
DEFAULT: 0 KB
This specifies the maximum size for an HTTP request body.
In other words, the maximum size of a PUT/POST request.
A user who attempts to send a request with a body larger
than this limit receives an "Invalid Request" error message.
If you set this parameter to a zero (the default), there will
be no limit imposed.