Amos Jeffries wrote:
On Wed, 10 Feb 2010 10:39:18 -0500, Matthew Morgan
atcs.matt...@gmail.com
wrote:
Here is the patch to add acl support to range_offset_limit. It is being
parsed using the same data types as reply_body_max_size, which means the
limit value gets run
tor 2010-02-11 klockan 08:33 -0500 skrev Matthew Morgan:
I may be misunderstanding you here, but not specifying
range_offset_limit makes it default to 0, which only downloads what the
client asks for no matter what. -1 makes it download the whole object
regardless of the range asked for
Henrik Nordström wrote:
tor 2010-02-11 klockan 08:33 -0500 skrev Matthew Morgan:
I may be misunderstanding you here, but not specifying
range_offset_limit makes it default to 0, which only downloads what the
client asks for no matter what. -1 makes it download the whole object
regardless
Here is the patch to add acl support to range_offset_limit. It is being
parsed using the same data types as reply_body_max_size, which means the
limit value gets run through parseBytesLine64, and the acl is optional.
If people are using the old global style of range_offset_limit, they
On Wed, 10 Feb 2010 10:39:18 -0500, Matthew Morgan
atcs.matt...@gmail.com
wrote:
Here is the patch to add acl support to range_offset_limit. It is being
parsed using the same data types as reply_body_max_size, which means the
limit value gets run through parseBytesLine64, and the acl is
