[nginx] nginx-1.9.7-RELEASE

details: http://hg.nginx.org/nginx/rev/54117529e40b branches: changeset: 6295:54117529e40b user: Maxim Dounin date: Tue Nov 17 17:50:56 2015 +0300 description: nginx-1.9.7-RELEASE diffstat: docs/xml/nginx/changes.xml | 76 ++ 1 files ch

[nginx] release-1.9.7 tag

details: http://hg.nginx.org/nginx/rev/4221623f2e46 branches: changeset: 6296:4221623f2e46 user: Maxim Dounin date: Tue Nov 17 17:50:57 2015 +0300 description: release-1.9.7 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diffs (8 lines): diff --gi

[nginx] Handled EINTR from write() and pwrite() syscalls.

details: http://hg.nginx.org/nginx/rev/5170c3040ce1 branches: changeset: 6299:5170c3040ce1 user: Valentin Bartenev date: Tue Nov 17 19:01:41 2015 +0300 description: Handled EINTR from write() and pwrite() syscalls. This is in addition to 6fce16b1fc10. diffstat: src/os/unix/ngx_fi

[nginx] Adjusted file->sys_offset after the write() syscall.

details: http://hg.nginx.org/nginx/rev/8f6d753c1953 branches: changeset: 6298:8f6d753c1953 user: Valentin Bartenev date: Tue Nov 17 19:01:41 2015 +0300 description: Adjusted file->sys_offset after the write() syscall. This fixes suboptimal behavior caused by surplus lseek() for sequ

[nginx] Moved file writev() handling code to a separate function.

details: http://hg.nginx.org/nginx/rev/be6af0906a4d branches: changeset: 6300:be6af0906a4d user: Valentin Bartenev date: Tue Nov 17 19:01:41 2015 +0300 description: Moved file writev() handling code to a separate function. No functional changes. diffstat: src/os/unix/ngx_files.c

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/92482faf5d8a branches: changeset: 6297:92482faf5d8a user: Valentin Bartenev date: Tue Nov 17 19:01:41 2015 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 line

[nginx] Used the pwritev() syscall for writing files where possi...

details: http://hg.nginx.org/nginx/rev/b5a87b51be24 branches: changeset: 6301:b5a87b51be24 user: Valentin Bartenev date: Tue Nov 17 19:01:41 2015 +0300 description: Used the pwritev() syscall for writing files where possible. It is more effective, because it doesn't require a separa

[nginx] Missing "variable" word added.

details: http://hg.nginx.org/nginx/rev/bec5b3093337 branches: changeset: 6302:bec5b3093337 user: Maxim Dounin date: Tue Nov 17 19:41:39 2015 +0300 description: Missing "variable" word added. diffstat: docs/xml/nginx/changes.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletion

Mark stale cache content as "invalid" on non-cacheable responses

Hi, Context: consider nginx used as a cache with proxy_cache_use_stale set to 'http_500' and the 'updating' parameter set i.e. it caches errors and serves the stale content while updating. Suppose the upstream temporarily responds with HTTP 504 and Cache-Control being max-age=3. The error gets c

Re: ngx_ext_rename_file: remove the target file if ngx_copy_file() fails

Hi, Sorry for late response. Maxim Dounin wrote: > ... > > By calling ngx_delete_file() at this point, you do this for all > errors returned by ngx_copy_file(), including cases when it wasn't > able to open a destination file for some reason. This will result > in additional confusing error

[nginx_gzip_static] Necessity to create empty file with always option.

Hi guys! I have the following weird situation: Several files with .gz extension are on disk and I have a location were requests are processed that do not include it, so I set the option gzip_static to always and also installed the gunzip module. The problem is, I still need to create EMPTY files w

Re: Mark stale cache content as "invalid" on non-cacheable responses

Hello! On Tue, Nov 17, 2015 at 05:25:30PM +, Mindaugas Rasiukevicius wrote: > Hi, > > Context: consider nginx used as a cache with proxy_cache_use_stale set > to 'http_500' and the 'updating' parameter set i.e. it caches errors and > serves the stale content while updating. Suppose the upst

Re: [nginx_gzip_static] Necessity to create empty file with always option.

On Tuesday 17 November 2015 19:15:43 Richard Fussenegger wrote: > Hi guys! > > I have the following weird situation: Several files with .gz extension > are on disk and I have a location were requests are processed that do > not include it, so I set the option gzip_static to always and also > insta

Re: [nginx_gzip_static] Necessity to create empty file with always option.

Thanks for the answer and solution! Sorry for using the wrong mailing list, will not happen again. Richard On 11/17/2015 7:29 PM, Valentin V. Bartenev wrote: > On Tuesday 17 November 2015 19:15:43 Richard Fussenegger wrote: >> Hi guys! >> >> I have the following weird situation: Several files wi

Re: Mark stale cache content as "invalid" on non-cacheable responses

Maxim Dounin wrote: > > Context: consider nginx used as a cache with proxy_cache_use_stale set > > to 'http_500' and the 'updating' parameter set i.e. it caches errors and > > serves the stale content while updating. Suppose the upstream > > temporarily responds with HTTP 504 and Cache-Control be