[PATCH] chroot directive for unix

2014-08-13 Thread Connor Worley
# HG changeset patch # User Connor Worley # Date 1407983583 14400 # Wed Aug 13 22:33:03 2014 -0400 # Node ID 342f712f72ceaeed3a5169fde96beb2a9950944a # Parent 92490a725fef588939abfe0e1fe89cda0788d02d chroot directive for unix Adds a chroot directive that calls chroot on worker processes for

Re: if-range issue

2014-08-13 Thread Anatoli Marinov
The patch change the behavior for more liberal direction :) On Wed, Aug 13, 2014 at 2:08 PM, Anatoli Marinov wrote: > I know this, but I used nginx as a reverse proxy and Etag comes from > remote server through nginx upstream. In general I do not have any control > on its value. Nginx uses this

Re: if-range issue

2014-08-13 Thread Anatoli Marinov
I know this, but I used nginx as a reverse proxy and Etag comes from remote server through nginx upstream. In general I do not have any control on its value. Nginx uses this value as it is sent from the other server. The file is cached with it and also this value is send to all http clients. On W

Re: if-range issue

2014-08-13 Thread Roman Arutyunyan
Hello, Etag value must be a quoted string. Please add double quotes to ETag and If-Range arguments and try again. RFC7232 / Section 2.3 ETag = entity-tag entity-tag = [ weak ] opaque-tag weak = %x57.2F ; "W/", case-sensitive opaque-tag = DQUOTE *etagc DQUOTE

if-range issue

2014-08-13 Thread Anatoli Marinov
Hello colleagues, Yesterday I found an issue with latest chrome and nginx 1.6.0. For the following request nginx returns 200 OK instead of 206 partial response: REQUEST GET /test.mp4 HTTP/1.1 Range: bytes=53037809-53037867 User-Agent: curl/7.33.0 Host: mydomain.com Accept: */* If-Range: 99f71760ac

[PATCH]Upstream: avoided directly terminating the connection.

2014-08-13 Thread flygoast
# HG changeset patch # User FengGu # Date 1407912835 -28800 # Wed Aug 13 14:53:55 2014 +0800 # Node ID 9dd4e38fcce05bcbba4747873a579bc2c9392dd2 # Parent 92490a725fef588939abfe0e1fe89cda0788d02d Upstream: avoided directly terminating the connection. When memory allocation failed in ngx_http