Nginx 1.13.4 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 2017-08-08, the mainline version 1.13.4 was released at nginx.org. Also, the upstream changelog is as follows:
Changes with nginx 1.13.4 – 08 Aug 2017
- ) Feature: the ngx_http_mirror_module.
- ) Bugfix: client connections might be dropped during configuration testing when using the “reuseport” parameter of the “listen” directive on Linux.
- ) Bug fix: request body might not be available in subrequests if it was saved to a file and proxying was used.
- ) Bugfix: cleaning cache based on the “max_size” parameter did not work on Windows.
- ) Bug fix: any shared memory allocation required 4096 bytes on Windows.
- ) Bugfix: nginx worker might be terminated abnormally when using the “zone” directive inside the “upstream” block on Windows.
—
Maxim Dounin
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.
Consequently, you may Download Nginx 1.13.4 for Windows (32-bit & 64-bit versions) here.
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.
Tweet This
