Nginx 1.15.6 32-bit and 64-bit builds for Windows are now available for free download.
As usual, packages were built using the upstream mainline branch’s source code. “Engine x” is a high performance web server. It is also a caching proxy and a Layer 7 load balancing solution. Millions of web sites on the Internet use and benefit from Nginx while offering extreme performance, scalability, reliability, flexibility, and security.
On 06 November 2018, the mainline version of Nginx 1.15.6, was released at nginx.org. Also, the upstream changelog is as follows:
Changes with nginx 1.15.6 — 06 November 2018
- ) Security: when using HTTP/2 a client might cause excessive memory consumption (CVE-2018-16843) and CPU usage (CVE-2018-16844).
- ) Security: processing of a specially crafted mp4 file with the ngx_http_mp4_module might result in worker process memory disclosure (CVE-2018-16845).
- ) Feature: the “proxy_socket_keepalive”, “fastcgi_socket_keepalive”, “grpc_socket_keepalive”, “memcached_socket_keepalive”, “scgi_socket_keepalive”, and “uwsgi_socket_keepalive” directives.
- ) Bugfix: if nginx was built with OpenSSL 1.1.0 and used with OpenSSL 1.1.1, the TLS 1.3 protocol was always enabled.
- ) Bugfix: working with gRPC backends might result in excessive memory consumption.
Due to the build process, these Windows install files are provided to support legacy users. In other words, those who still use the Cygwin based builds. I started building long before official builds became available. Initially there was no other way to run on Windows. But now, official native Windows builds are available and supported at nginx.org. So please use the official builds if you are new to Nginx on Windows. Once again, they are fully supported and available for download at nginx.org.
Furthermore, please check out the FAQ: Frequently Asked Questions.
The questions are updated continually as they are received. Therefore the answers may help you. Additionally, if you have other questions that are not on the FAQ please feel free to ask or leave a comment below.
In conclusion, I always welcome and appreciate your feedback for improvements and enhancements. Thank you.