HTTP/3: restricted symbols in header names. As per HTTP/3 draft 27, a request or response containing uppercase header field names MUST be treated as malformed. Also, existing rules applied when parsing HTTP/1 header names are also applied to HTTP/3 header names: - null character is not allowed - underscore character may or may not be treated as invalid depending on the value of "underscores_in_headers" - all non-alphanumeric characters with the exception of '-' are treated as invalid Also, the r->locase_header field is now filled while parsing an HTTP/3 header. Error logging for invalid headers is fixed as well.

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


all:
	cd $(OPENSSL)

	perl Configure BC-32 no-shared --prefix=openssl $(OPENSSL_OPT)

	ms\do_nasm

	$(MAKE) -f ms\bcb.mak
	$(MAKE) -f ms\bcb.mak install

	# Borland's make does not expand "[ch]" in
	#    copy "inc32\openssl\*.[ch]" "openssl\include\openssl"
	copy inc32\openssl\*.h openssl\include\openssl