Mercurial > hg > nginx-quic
view src/core/ngx_sha1.h @ 4162:fb1375e8b68c stable-1.0
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.
author | Igor Sysoev <igor@sysoev.ru> |
---|---|
date | Fri, 30 Sep 2011 14:06:08 +0000 |
parents | 27d4ed42e49d |
children | d620f497c50f |
line wrap: on
line source
/* * Copyright (C) Igor Sysoev */ #ifndef _NGX_SHA1_H_INCLUDED_ #define _NGX_SHA1_H_INCLUDED_ #include <ngx_config.h> #include <ngx_core.h> #if (NGX_HAVE_OPENSSL_SHA1_H) #include <openssl/sha.h> #else #include <sha.h> #endif typedef SHA_CTX ngx_sha1_t; #define ngx_sha1_init SHA1_Init #define ngx_sha1_update SHA1_Update #define ngx_sha1_final SHA1_Final #endif /* _NGX_SHA1_H_INCLUDED_ */