Proper setting of read->eof in pipe code. Setting read->eof to 0 seems to be just a typo. It appeared in nginx-0.0.1-2003-10-28-18:45:41 import (r164), while identical code in ngx_recv.c introduced in the same import do actually set read->eof to 1. Failure to set read->eof to 1 results in EOF not being generally detectable from connection flags. On the other hand, kqueue won't report any read events on such a connection since we use EV_CLEAR. This resulted in read timeouts if such connection was cached and used for another request.

# Copyright (C) Igor Sysoev


CFLAGS = -nologo -O2 -Ob1 -Oi -Gs $(LIBC) $(CPU_OPT) -D L_ENDIAN

!IF "$(SHA1_ASM)" == "YES"

sha1.lib:
	cd $(SHA1)
	cl -c $(CFLAGS) -D SHA1_ASM sha1dgst.c
	link -lib -out:sha1.lib sha1dgst.obj asm/s-win32.obj

!ELSE

sha1.lib:
	cd $(SHA1)
	cl -c $(CFLAGS) sha1dgst.c
	link -lib -out:sha1.lib sha1dgst.obj

!ENDIF