<div dir="ltr">Hello Nginx users,<br><br>Now available: Nginx 1.13.6 for Windows <a href="https://kevinworthington.com/nginxwin1136">https://kevinworthington.com/nginxwin1136</a> (32-bit and 64-bit versions)<br><br>These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at <a href="http://nginx.org">nginx.org</a>.<br><br>Announcements are also available here:<br>Twitter <a href="http://twitter.com/kworthington">http://twitter.com/kworthington</a><br>Google+ <a href="https://plus.google.com/+KevinWorthington/">https://plus.google.com/+KevinWorthington/</a><br><br>Thank you,<br>Kevin<br>--<br>Kevin Worthington<br>kworthington *@* (gmail]  [dot} {com)<br><a href="https://kevinworthington.com/">https://kevinworthington.com/</a><br><a href="https://twitter.com/kworthington">https://twitter.com/kworthington</a><br><a href="https://plus.google.com/+KevinWorthington/">https://plus.google.com/+KevinWorthington/</a><br><br><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 10, 2017 at 1:47 PM, Kevin Worthington <span dir="ltr"><<a href="mailto:kworthington@gmail.com" target="_blank">kworthington@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello Nginx users,<br><br>Now available: Nginx 1.13.6 for Windows <a href="https://kevinworthington.com/nginxwin1136" target="_blank">https://kevinworthington.com/<wbr>nginxwin1136</a> (32-bit and 64-bit versions)<br><br>These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at <a href="http://nginx.org" target="_blank">nginx.org</a>.<br><br>Announcements are also available here:<br>Twitter <a href="http://twitter.com/kworthington" target="_blank">http://twitter.com/<wbr>kworthington</a><br>Google+ <a href="https://plus.google.com/+KevinWorthington/" target="_blank">https://plus.google.com/+<wbr>KevinWorthington/</a><br><br>Thank you,<br>Kevin<br>--<br>Kevin Worthington<br>kworthington *@* (gmail]  [dot} {com)<br><a href="https://kevinworthington.com/" target="_blank">https://kevinworthington.com/</a><br><a href="https://twitter.com/kworthington" target="_blank">https://twitter.com/<wbr>kworthington</a><br><a href="https://plus.google.com/+KevinWorthington/" target="_blank">https://plus.google.com/+<wbr>KevinWorthington/</a><div><div class="gmail-h5"><br><br><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 10, 2017 at 11:40 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru" target="_blank">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Changes with nginx 1.13.6                                        10 Oct 2017<br>
<br>
    *) Bugfix: switching to the next upstream server in the stream module<br>
       did not work when using the "ssl_preread" directive.<br>
<br>
    *) Bugfix: in the ngx_http_v2_module.<br>
       Thanks to Piotr Sikora.<br>
<br>
    *) Bugfix: nginx did not support dates after the year 2038 on 32-bit<br>
       platforms with 64-bit time_t.<br>
<br>
    *) Bugfix: in handling of dates prior to the year 1970 and after the<br>
       year 10000.<br>
<br>
    *) Bugfix: in the stream module timeouts waiting for UDP datagrams from<br>
       upstream servers were not logged or logged at the "info" level<br>
       instead of "error".<br>
<br>
    *) Bugfix: when using HTTP/2 nginx might return the 400 response without<br>
       logging the reason.<br>
<br>
    *) Bugfix: in processing of corrupted cache files.<br>
<br>
    *) Bugfix: cache control headers were ignored when caching errors<br>
       intercepted by error_page.<br>
<br>
    *) Bugfix: when using HTTP/2 client request body might be corrupted.<br>
<br>
    *) Bugfix: in handling of client addresses when using unix domain<br>
       sockets.<br>
<br>
    *) Bugfix: nginx hogged CPU when using the "hash ... consistent"<br>
       directive in the upstream block if large weights were used and all or<br>
       most of the servers were unavailable.<br>
<span class="gmail-m_7204948604447696638gmail-HOEnZb"><font color="#888888"><br>
<br>
--<br>
Maxim Dounin<br>
<a href="http://nginx.org/" rel="noreferrer" target="_blank">http://nginx.org/</a><br>
______________________________<wbr>_________________<br>
nginx-announce mailing list<br>
<a href="mailto:nginx-announce@nginx.org" target="_blank">nginx-announce@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx-announce" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailm<wbr>an/listinfo/nginx-announce</a><br>
</font></span></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div>