aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* nginx-1.1.13-RELEASErelease-1.1.13Maxim Dounin2012-01-16
|
* Updated OpenSSL version used for win32 build.Maxim Dounin2012-01-16
|
* 2012 year.Igor Sysoev2012-01-16
|
* Fixed division by zero exception in ngx_hash_init().Valentin Bartenev2012-01-16
| | | | | | | | | | | | | | | | The ngx_hash_init() function did not expect call with zero elements count, which caused FPE error on configs with an empty "types" block in http context and "types_hash_max_size" > 10000. Example configuration to reproduce: events { } http { types_hash_max_size 10001; types {} server {} }
* Fixed sched_setaffinity(2) to correctly pass size.Maxim Dounin2012-01-16
| | | | | | Second argument (cpusetsize) is size in bytes, not in bits. Previously used constant 32 resulted in reading of uninitialized memory and caused EINVAL to be returned on some Linux kernels.
* Fixed handling of mp4 above 2G and 32bit offsets (ticket #84).Maxim Dounin2012-01-16
|
* Fixed proxy_cache_use_stale in "no live upstreams" case.Maxim Dounin2012-01-16
|
* Added support for TLSv1.1, TLSv1.2 in ssl_protocols directive.Maxim Dounin2012-01-11
| | | | | | Support for TLSv1.1 and TLSv1.2 protocols was introduced in OpenSSL 1.0.1 (-beta1 was recently released). This change makes it possible to disable these protocols and/or enable them without other protocols.
* Fixed limit_req burst/nodelay inheritance (ticket #76).Maxim Dounin2012-01-11
| | | | The problem was introduced in r4381 (1.1.12).
* Fixed: proxy_redirect with regex might broke Refresh header.Valentin Bartenev2012-01-10
| | | | | The problem was localized in ngx_http_proxy_rewrite_redirect_regex() handler function which did not take into account prefix when overwriting header value.
* Changed ngx_log_debugN() macros to verify the number of argumentsRuslan Ermilov2012-01-10
| | | | when built with debugging.
* Fixed configure with system PCRE library on Solaris.Valentin Bartenev2011-12-29
| | | | The bug has been introduced in r4389.
* Some questionable optomizations flags for icc were removedMaxim Konovalov2011-12-29
| | | | in order to simplify support of its future versions.
* Fixed punctuation.Maxim Dounin2011-12-28
|
* libraries versions updatedSergey Budnevitch2011-12-27
|
* zlib license file include fixedSergey Budnevitch2011-12-27
|
* Version bump.Maxim Dounin2011-12-27
|
* release-1.1.12 tagMaxim Dounin2011-12-26
|
* nginx-1.1.12-RELEASErelease-1.1.12Maxim Dounin2011-12-26
|
* Added support for regex study and PCRE JIT (ticket #41) optimizations onValentin Bartenev2011-12-26
| | | | configuration phase.
* Fixed build without debug.Maxim Dounin2011-12-26
|
* Cache lock support for fastcgi, scgi, uwsgi.Maxim Dounin2011-12-26
|
* Cache locks initial implementation.Maxim Dounin2011-12-26
| | | | | | | | | | | | | | | | | | | | | | New directives: proxy_cache_lock on/off, proxy_cache_lock_timeout. With proxy_cache_lock set to on, only one request will be allowed to go to upstream for a particular cache item. Others will wait for a response to appear in cache (or cache lock released) up to proxy_cache_lock_timeout. Waiting requests will recheck if they have cached response ready (or are allowed to run) every 500ms. Note: we intentionally don't intercept NGX_DECLINED possibly returned by ngx_http_file_cache_read(). This needs more work (possibly safe, but needs further investigation). Anyway, it's exceptional situation. Note: probably there should be a way to disable caching of responses if there is already one request fetching resource to cache (without waiting at all). Two possible ways include another cache lock option ("no_cache") or using proxy_no_cache with some supplied variable. Note: probably there should be a way to lock updating requests as well. For now "proxy_cache_use_stale updating" is available.
* Fixed interaction of limit_rate and sendfile_max_chunk.Maxim Dounin2011-12-26
| | | | | | | | | | It's possible that configured limit_rate will permit more bytes per single operation than sendfile_max_chunk. To protect disk from takeover by a single client it is necessary to apply sendfile_max_chunk as a limit regardless of configured limit_rate. See here for report (in Russian): http://mailman.nginx.org/pipermail/nginx-ru/2010-March/032806.html
* Fixed throughput problems with large limit_rate.Maxim Dounin2011-12-26
| | | | | Previous attempt to fix this was in r1658 (0.6.18), though that one wasn't enough (it was a noop).
* Fixed mp4 if first entry in stsc was skipped (ticket #72).Maxim Dounin2011-12-26
| | | | | If first entry in stsc atom was skipped, and seek was to chunk boundary, than first_chunk in the generated stsc table wasn't set to 1.
* SSI: added regex captures support in the expression of the "if" command.Valentin Bartenev2011-12-25
|
* Fixed limit_conn_log_level/limit_req_log_level inheritance.Valentin Bartenev2011-12-25
| | | | | The directives did not work if there were no limit_conn/limit_req specified on the same level.
* Added the HTTPS fastcgi_param to fastcgi.conf.Valentin Bartenev2011-12-25
|
* Words duplications removed.Maxim Konovalov2011-12-24
|
* Proxy: made proxy_pass with variables more consistent.Maxim Dounin2011-12-23
| | | | | | | | | If proxy_pass was used with variables and there was no URI component, nginx always used unparsed URI. This isn't consistent with "no variables" case, where e.g. rewrites are applied even if there is no URI component. Fix is to use the same logic in both cases, i.e. only use unparsed URI if it's valid and request is the main one.
* configure on Solaris fixedSergey Budnevitch2011-12-20
|
* Added clearing of r->valid_unparsed_uri on internal redirects.Maxim Dounin2011-12-19
| | | | | | | | | | | | | | | | | | This resolves issue with try_files (see ticket #70), configuration like location / { try_files $uri /index.php; } location /index.php { proxy_pass http://backend; } caused nginx to use original request uri in a request to a backend. Historically, not clearing of the r->valid_unparsed_uri on internal redirect was a feature: it allowed to pass the same request to (another) upstream server via error_page redirection. Since then named locations appeared though, and it's time to start resetting r->valid_unparsed_uri on internal redirects. Configurations still using this feature should be converted to use named locations instead. Patch by Lanshun Zhou.
* SSI bugfix: the "if" command did not work inside the "block" command andValentin Bartenev2011-12-19
| | | | produced parsing errors.
* Scgi: removed error if there is no Status header.Maxim Dounin2011-12-19
| | | | | | | The SCGI specification doesn't specify format of the response, and assuming CGI specs should be used there is no reason to complain. RFC 3875 explicitly states that "A Status header field is optional, and status 200 'OK' is assumed if it is omitted".
* Scgi: removed duplicate function declaration.Maxim Dounin2011-12-19
|
* Fixed incorrect use of r->http_version in scgi module.Maxim Dounin2011-12-19
| | | | | | | | | | | The r->http_version is a version of client's request, and modules must not set it unless they are really willing to downgrade protocol version used for a response (i.e. to HTTP/0.9 if no response headers are available). In neither case r->http_version may be upgraded. The former code downgraded response from HTTP/1.1 to HTTP/1.0 for no reason, causing various problems (see ticket #66). It was also possible that HTTP/0.9 requests were upgraded to HTTP/1.0.
* Version bump.Maxim Dounin2011-12-19
|
* release-1.1.11 tagMaxim Dounin2011-12-12
|
* nginx-1.1.11-RELEASErelease-1.1.11Maxim Dounin2011-12-12
|
* Fixed RELEASE target again.Maxim Dounin2011-12-12
|
* Fixed RELEASE target to correctly call "release" one.Maxim Dounin2011-12-12
|
* Cache: only complain on long locked entries.Maxim Dounin2011-12-12
| | | | | | | | | | There have been multiple reports of cases where a real locked entry was removed, resulting in a segmentation fault later in a worker which locked the entry. It looks like default inactive timeout isn't enough in real life. For now just ignore such locked entries, and move them to the top of the inactive queue to allow processing of other entries.
* Cache: handling of cache files with long headers.Maxim Dounin2011-12-12
| | | | | | | | | | There are two possible situations which can lead to this: response was cached with bigger proxy_buffer_size value (and nginx was restared since then, i.e. shared memory zone content was lost), or due to the race in the cache update code (see [1]) we've end up with fcn->body_start from a different response stored in shared memory zone. [1] http://mailman.nginx.org/pipermail/nginx-devel/2011-September/001287.html
* Cache: obsolete code removed.Maxim Dounin2011-12-12
| | | | | | The ngx_http_cache() and ngx_http_no_cache_set_slot() functions were replaced by ngx_http_test_predicates() and ngx_http_set_predicate_slot() in 0.8.46 and no longer used since then.
* Renamed some constants to improve readability, no functional changes.Ruslan Ermilov2011-12-12
|
* Proxy: added variables and regexp support to the first parameter ofValentin Bartenev2011-12-12
| | | | the "proxy_redirect" directive.
* Microoptimization of sendfile(2) usage under FreeBSD.Maxim Dounin2011-12-11
| | | | | | | FreeBSD kernel checks headers/trailers pointer against NULL, not corresponding count. Passing NULL if there are no headers/trailers helps to avoid unneeded work in kernel, as well as unexpected 0 bytes GIO in traces.
* Fixed: some of $sent_http_* variables may contain header entries that actuallyValentin Bartenev2011-12-09
| | | | | | | | | haven't been sent to a client. The ngx_http_variable_headers() and ngx_http_variable_unknown_header() functions did not ignore response header entries with zero "hash" field. Thanks to Yichun Zhang (agentzh).
* Added HTTPS param with Apache-like behaviour to fastcgi/scgi/uwsgi_params ↵Valentin Bartenev2011-12-09
| | | | (fixes #38).
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-24 21:46:50 +0000