Hi Maxim,
Thanks for committing that. And again for your help.
Cheers,
Kevin
--
Kevin Worthington
http://kevinworthington.com/
http://twitter.com/kworthington
On Mon, Aug 5, 2013 at 3:42 AM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Aug 03, 2013 at 12:31:54PM -0400, Kevin Worthington wrote:
>
Hello!
On Sat, Aug 03, 2013 at 12:31:54PM -0400, Kevin Worthington wrote:
> Hi Maxim,
>
> Thanks so much. Your patch worked great.
>
> The build was failing without that change.
>
> Is there any way that patch can be incorporated into the main source, so
> that it doesn't happen again in 1.5.4
Hello Nginx users,
Now available: Nginx 1.5.3 for Windows http://goo.gl/qiz6kq (32-bit and
64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announcements are also
http://kevinworthington.com/
http://twitter.com/kworthington
On Sat, Aug 3, 2013 at 6:47 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Aug 02, 2013 at 09:17:03PM -0400, Kevin Worthington wrote:
>
> > I'm trying to build nginx 1.5.3 on Cygwin using Windows 7. I see the
>
Hello!
On Fri, Aug 02, 2013 at 09:17:03PM -0400, Kevin Worthington wrote:
> I'm trying to build nginx 1.5.3 on Cygwin using Windows 7. I see the
> following output during "make":
[...]
> cc1: warnings being treated as errors
> src/core/ngx_inet.c: In function
Hello,
I'm trying to build nginx 1.5.3 on Cygwin using Windows 7. I see the
following output during "make":
cc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g
-D FD_
SETSIZE=2048 -I src/core -I src/event -I src/event/modules -I src/os/unix
-I ~/o
penssl-
Thanks for your reply.
-邮件原件-
发件人: nginx-boun...@nginx.org [mailto:nginx-boun...@nginx.org] 代表 Yichun Zhang
(agentzh)
发送时间: 2013年7月31日 13:00
收件人: nginx@nginx.org
主题: Re: nginx-1.5.3
Hello!
On Tue, Jul 30, 2013 at 7:49 PM, 卫越 wrote:
>>*) Change: now after receiving an inco
Hello!
On Tue, Jul 30, 2013 at 7:49 PM, 卫越 wrote:
>>*) Change: now after receiving an incomplete response from a backend
>> server nginx tries to send an available part of the response to a
>> client, and then closes client connection.
>
> It is obviously different from previous n
>*) Change: now after receiving an incomplete response from a backend
> server nginx tries to send an available part of the response to a
> client, and then closes client connection.
It is obviously different from previous nginx, but I wonder why nginx made
this change.
__
Changes with nginx 1.5.3 30 Jul 2013
*) Change in internal API: now u->length defaults to -1 if working with
backends in unbuffered mode.
*) Change: now after receiving an incomplete response from a backend
server nginx tries to s
10 matches
Mail list logo