aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Fixed Upgrade header clearing with proxy_cache.Maxim Dounin2011-11-14
| | | | This was missed in proxy HTTP/1.1 support commit (r4127).
* Fixed proxy_set_header inheritance with proxy_set_body.Maxim Dounin2011-11-14
|
* Fixed proxy_set_header inheritance with proxy_cache (ticket #45).Maxim Dounin2011-11-14
| | | | | | | | | | | | | | | | | | | | | | | | | | Headers cleared with cache enabled (If-Modified-Since etc.) might be cleared in unrelated servers/locations without proxy_cache enabled if proxy_cache was used in some server/location. Example config which triggered the problem: proxy_set_header X-Test "test"; server { location /1 { proxy_cache name; proxy_pass ... } } server { location /2 { proxy_pass ... } } Another one: server { proxy_cache name; location /1 { proxy_pass ... } location /2 { proxy_cache off; proxy_pass ... } } In both cases If-Modified-Since header wasn't sent to backend in location /2. Fix is to not modify conf->headers_source, but instead merge user-supplied headers from conf->headers_source and default headers (either cache or not) into separate headers_merged array.
* Fixed NGX_CONF_TAKE1/NGX_CONF_FLAG misuse.Sergey Budnevitch2011-11-14
|
* Limit zone: added the "limit_conn_zone" directive.Valentin Bartenev2011-11-10
| | | | | It supersedes old "limit_zone" directive (deprecated accordingly) and uses syntax consistent with the "limit_req_zone" directive.
* Limit zone: support for multiple "limit_conn" limits.Valentin Bartenev2011-11-10
|
* Limit zone: rbtree lookup moved to a separate function.Valentin Bartenev2011-11-10
| | | | No functional changes.
* Changed error message to be more appropriate in the imaginaryRuslan Ermilov2011-11-10
| | | | "open_file_cache max=0" case.
* Belatedly fixed language in 1.1.7 relnotes.Ruslan Ermilov2011-11-09
|
* Fixed compression pointer processing in DNS response greater than 255 bytes.Igor Sysoev2011-11-09
| | | | Thanks to Ben Hawkes.
* Fix of "keepalive_disable" directive.Igor Sysoev2011-11-08
|
* The "image_filter_sharpen" directive.Igor Sysoev2011-11-08
|
* Ancient incomplete ngx_http_status_module removal.Igor Sysoev2011-11-01
|
* Version bump.Igor Sysoev2011-11-01
|
* release-1.1.7 tagIgor Sysoev2011-10-31
|
* nginx-1.1.7-RELEASErelease-1.1.7Igor Sysoev2011-10-31
|
* Silently ignoring a stale global SSL error left after disabled renegotiation.Igor Sysoev2011-10-31
|
* Fixed documentation pointer.Ruslan Ermilov2011-10-31
|
* Fixed segfault on configuration testing with ssl (ticket #37).Maxim Dounin2011-10-31
| | | | | | | | | | | The following config caused segmentation fault due to conf->file not being properly set if "ssl on" was inherited from the http level: http { ssl on; server { } }
* Event pipe: reduced number of file buffers used.Maxim Dounin2011-10-31
| | | | | | | | If possible we now just extend already present file buffer in p->out chain instead of keeping ngx_buf_t for each buffer we've flushed to disk. This saves about 120 bytes of memory per buffer flushed to disk, and resolves high CPU usage observed in edge cases (due to coalescing these buffers on send).
* Event pipe: fixes for complex protocols.Maxim Dounin2011-10-31
| | | | | | | | | | | | | | | | 1. In ngx_event_pipe_write_chain_to_temp_file() make sure to fully write all shadow buffers up to last_shadow. With this change recycled buffers cannot appear in p->out anymore. This also fixes segmentation faults observed due to ngx_event_pipe_write_chain_to_temp() not freeing any raw buffers while still returning NGX_OK. 2. In ngx_event_pipe_write_to_downstream() we now properly check for busy size as a size of buffers, not a size of data in these buffers. This fixes situations where all available buffers became busy (including segmentation faults due to this). 3. The ngx_event_pipe_free_shadow_raw_buf() function is dropped. It's incorrect and not needed.
* Adding m4a and m4v MIME types (closed #42).Igor Sysoev2011-10-28
|
* Revamped "configure --help" text.Ruslan Ermilov2011-10-26
|
* Fix of building by Microsoft Visual C++ 10 compiler.Igor Sysoev2011-10-26
|
* Decrease of log level of some SSL handshake errors.Igor Sysoev2011-10-25
|
* Fixed port range checking.Ruslan Ermilov2011-10-25
|
* Fixed range checking for the "somaxconn" sysctl.Ruslan Ermilov2011-10-25
|
* Support of several servers in the "resolver" directive.Igor Sysoev2011-10-24
| | | | Patch by Kirill A. Korinskiy.
* Using of junk value in slab allocator similar to modern FreeBSD values.Igor Sysoev2011-10-24
|
* malloc() debugging on MacOSX.Igor Sysoev2011-10-24
|
* FreeBSD's MALLOC_OPTIONS must be set before any malloc() call.Igor Sysoev2011-10-24
| | | | The bug has been introduced in r3799.
* Fixed another return in unix ngx_write_chain_to_file().Maxim Dounin2011-10-21
| | | | | Previous patch missed special case for one iovec, it needs total bytes written to be returned as well.
* Fixed unix ngx_write_chain_to_file() to return total bytes written.Maxim Dounin2011-10-20
| | | | | | Previously result of last iteration's writev() was returned. This was unnoticed as return value was only used if chain contained only one or two buffers.
* Fixing conflict with SDK off_t definition.Igor Sysoev2011-10-20
|
* Recent SDKs allow to build IPV6 only for Windows XP or above.Igor Sysoev2011-10-20
|
* Fixed "expires @time" with unknown last modified time (ticket #32).Maxim Dounin2011-10-17
|
* Fixed "expires @00h".Maxim Dounin2011-10-17
|
* Removal of incomplete draft documentation processing.Igor Sysoev2011-10-17
|
* Version bump.Igor Sysoev2011-10-17
|
* release-1.1.6 tagIgor Sysoev2011-10-17
|
* nginx-1.1.6-RELEASErelease-1.1.6Igor Sysoev2011-10-17
|
* Moving RELEASE target in more safe place.Igor Sysoev2011-10-17
|
* Added clearing of modules' contexts in ngx_http_named_location().Maxim Dounin2011-10-15
| | | | Patch by Yichun Zhang (agentzh).
* Fixed utf8 decode (ticket #25).Maxim Dounin2011-10-13
| | | | Patch by Alexey Kuts.
* Skipping location rewrite phase for server null location.Igor Sysoev2011-10-13
|
* Better recheck of dead upstream servers.Maxim Dounin2011-10-12
| | | | | | | | | | | | | | | | | | | Previously nginx used to mark backend again as live as soon as fail_timeout passes (10s by default) since last failure. On the other hand, detecting dead backend takes up to 60s (proxy_connect_timeout) in typical situation "backend is down and doesn't respond to any packets". This resulted in suboptimal behaviour in the above situation (up to 23% of requests were directed to dead backend with default settings). More detailed description of the problem may be found here (in Russian): http://mailman.nginx.org/pipermail/nginx-ru/2011-August/042172.html Fix is to only allow one request after fail_timeout passes, and mark backend as "live" only if this request succeeds. Note that with new code backend will not be marked "live" unless "check" request is completed, and this may take a while in some specific workloads (e.g. streaming). This is believed to be acceptable.
* Clear old Location header (if any) while adding a new one.Maxim Dounin2011-10-12
| | | | | This prevents incorrect behaviour when another redirect is issued within error_page 302 handler.
* Wording fix, "many data" is incorrect.Maxim Dounin2011-10-12
| | | | Noted by Piotr Sikora.
* Fixed two minor bugs in "types" parsing code.Ruslan Ermilov2011-10-12
|
* Fixed grammar in a comment.Ruslan Ermilov2011-10-12
|