summaryrefslogtreecommitdiffhomepage
path: root/src/os/unix/ngx_linux_aio_read.c
diff options
context:
space:
mode:
authorIgor Sysoev <igor@sysoev.ru>2011-09-30 14:06:08 +0000
committerIgor Sysoev <igor@sysoev.ru>2011-09-30 14:06:08 +0000
commit0b2b252cfbafe2744aa84953729105c8e7c1dc61 (patch)
tree1e09bf16f9358ebdae8dc5ef5700bfea8e9142ec /src/os/unix/ngx_linux_aio_read.c
parent66ef8eba590ab96429356650297e173f41396eff (diff)
downloadnginx-0b2b252cfbafe2744aa84953729105c8e7c1dc61.tar.gz
nginx-0b2b252cfbafe2744aa84953729105c8e7c1dc61.tar.bz2
Merging r4036, r4055, r4056, r4057, r4058, r4059, r4060, r4061, r4062, r4063,
r4064: Ranges related fixes: The "max_ranges" directive. "max_ranges 0" disables ranges support at all, "max_ranges 1" allows the single range, etc. By default number of ranges is unlimited, to be precise, 2^31-1. If client requests more ranges than "max_ranges" permits, nginx disables ranges and returns just the source response. If total size of all ranges is greater than source response size, then nginx disables ranges and returns just the source response. This fix should not affect well-behaving applications but will defeat DoS attempts exploiting malicious byte ranges. Now unsatisfiable ranges are processed according to RFC 2616.
Diffstat (limited to 'src/os/unix/ngx_linux_aio_read.c')
0 files changed, 0 insertions, 0 deletions