HTTP/2: send WINDOW_UPDATE instead of RST_STREAM with NO_ERROR. After the 92464ebace8e change, it has been discovered that not all clients follow the RFC and handle RST_STREAM with NO_ERROR properly. Notably, Chrome currently interprets it as INTERNAL_ERROR and discards the response. As a workaround, instead of RST_STREAM the maximum stream window update will be sent, which will let client to send up to 2 GB of a request body data before getting stuck on flow control. All the received data will be silently discarded. See for details: http://mailman.nginx.org/pipermail/nginx-devel/2016-April/008143.html https://bugs.chromium.org/p/chromium/issues/detail?id=603182

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


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

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

sha1.lib:
	cd $(SHA1)
	bcc32 -c $(CFLAGS) -DSHA1_ASM sha1dgst.c
	tlib sha1.lib +sha1dgst.obj +"asm\s-win32.obj"

!else

sha1.lib:
	cd $(SHA1)
	bcc32 -c $(CFLAGS) sha1dgst.c
	tlib sha1.lib +sha1dgst.obj

!endif