Memcached: stricten header validation. An invalid memcached reply that started with '\n' could cause segmentation fault. An invalid memcached reply "VALUE / 0 2\r?ok\r\nEND\r\n" was considered as a valid response. In addition, if memcached reports that the key was not found, set u->headers_in.content_length_n to 0. This ensures that ngx_http_memcached_filter() will not be called while previous code relied on always intercepting 404. Initialization of ctx->rest was moved to where it belongs.

# Copyright (C) Igor Sysoev
# Copyright (C) Nginx, Inc.


CFLAGS = -q -O2 -tWM $(CPU_OPT) -DL_ENDIAN

!if "$(MD5_ASM)" == "YES"

md5.lib:
	cd $(MD5)
	bcc32 -c $(CFLAGS) -DMD5_ASM md5_dgst.c
	tlib md5.lib +md5_dgst.obj +"asm\m-win32.obj"

!else

md5.lib:
	cd $(MD5)
	bcc32 -c $(CFLAGS) md5_dgst.c
	tlib md5.lib +md5_dgst.obj

!endif