nginx.git/src/http, branch release-1.1.12

Fixed build without debug.

2011-12-26T11:33:11+00:00

Cache lock support for fastcgi, scgi, uwsgi.

2011-12-26T11:16:19+00:00

Cache locks initial implementation.

2011-12-26T11:15:23+00:00

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.

2011-12-26T10:51:24+00:00

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.

2011-12-26T10:49:57+00:00

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).

2011-12-26T10:49:03+00:00

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.

2011-12-25T20:08:37+00:00

Fixed limit_conn_log_level/limit_req_log_level inheritance.

2011-12-25T19:32:31+00:00

The directives did not work if there were no limit_conn/limit_req specified on
the same level.

Proxy: made proxy_pass with variables more consistent.

2011-12-23T16:04:09+00:00

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.

Added clearing of r->valid_unparsed_uri on internal redirects.

2011-12-19T14:11:48+00:00

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.