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

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

SSI bugfix: the "if" command did not work inside the "block" command and

2011-12-19T13:28:22+00:00

produced parsing errors.

Scgi: removed error if there is no Status header.

2011-12-19T11:25:40+00:00

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.

2011-12-19T11:24:32+00:00

Fixed incorrect use of r->http_version in scgi module.

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

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.