[PATCH] Core: use NGX_FILE_ERROR when appropriate

2013-03-20 Thread Piotr Sikora
Hey guys, attached patch changes "if" tests to use "== NGX_FILE_ERROR" instead of "== -1" or "!= NGX_OK", because NGX_FILE_ERROR is defined as -1 on UNIX, but as 0 on Win32. This isn't much of an issue in patched code (only "ngx_fd_info()" test is actually reachable on Win32 and in worst case it m

[nginx] svn commit: r5123 - trunk/src/core

2013-03-20 Thread ru
Author: ru Date: 2013-03-20 18:07:25 + (Wed, 20 Mar 2013) New Revision: 5123 URL: http://trac.nginx.org/nginx/changeset/5123/nginx Log: Core: fixed resource leak if binary upgrade fails due to no memory. Found by Coverity (CID 992320). Modified: trunk/src/core/nginx.c Modified: trunk/sr

[nginx] svn commit: r5121 - trunk/src/os/win32

2013-03-20 Thread vbart
Author: vbart Date: 2013-03-20 10:18:26 + (Wed, 20 Mar 2013) New Revision: 5121 URL: http://trac.nginx.org/nginx/changeset/5121/nginx Log: Win32: disabled MSVC warning about '\0' not fitting into array. We believe that this warning produces more inconvience than real benefit. Here is an examp

[nginx] svn commit: r5120 - trunk/src/http

2013-03-20 Thread vbart
Author: vbart Date: 2013-03-20 09:36:27 + (Wed, 20 Mar 2013) New Revision: 5120 URL: http://trac.nginx.org/nginx/changeset/5120/nginx Log: URI processing code moved to a separate function. This allows to reuse it in the upcoming SPDY module. Modified: trunk/src/http/ngx_http_request.c M

Re: 100-continue and 401

2013-03-20 Thread Dmitry Petrov
Hi Luka, There was a post about similar problem on nginx forum with reply from Igor: http://forum.nginx.org/read.php?2,212533,212549#msg-212549 On Wed, Mar 20, 2013 at 12:44 PM, Luka Perkov wrote: > Hi Vladimir, > > On Tue, Mar 19, 2013 at 07:36:07PM +0400, Vladimir Shebordaev wrote: > > Both r

Re: 100-continue and 401

2013-03-20 Thread Luka Perkov
Hi Nick, On Tue, Mar 19, 2013 at 05:09:38PM +, Nick Kew wrote: > On 19 Mar 2013, at 12:31, Luka Perkov wrote: > > I'm using nginx as a frontend for my SCGI application and I want to > > $ curl -v -X POST -d "@/path/to/some/blob" http://127.0.0.1:8000/ > > * About to connect() to 127.0.0.1 port

Re: 100-continue and 401

2013-03-20 Thread Luka Perkov
Hi Vladimir, On Tue, Mar 19, 2013 at 07:36:07PM +0400, Vladimir Shebordaev wrote: > Both requests do look basically correct just like the nginx's and > curl's behavior. You didn't supply any credentials for > authentication to continue. I know I didn't. That is the example test, if my SCGI daemon