I have been testing nginx 1.6.0 as a reverse proxy with SPDY support. I
sometimes get empty responses. I have seen a bug report
(#428 (SPDY and Proxy Cache prematurely closes connections) – nginx) about this which seems to be in
line with what I have been seeing. It’s marked as fixed but there seems
some
confusion about whether this fix was accepted. I have also seen that
various
SPDY related issues were fixed in 1.7.x mainline and I was waiting for
1.6.1
in the hope that these would be retrofitted to 1.6.1.
So, I would just like to do if these empty response issues have been
addressed? It seems like a major stability concern.
On Tuesday 05 August 2014 11:04:15 mschipperheyn wrote:
I have been testing nginx 1.6.0 as a reverse proxy with SPDY support. I
sometimes get empty responses. I have seen a bug report
(#428 (SPDY and Proxy Cache prematurely closes connections) – nginx) about this which seems to be in
line with what I have been seeing. It’s marked as fixed but there seems some
confusion about whether this fix was accepted. I have also seen that various
SPDY related issues were fixed in 1.7.x mainline and I was waiting for 1.6.1
in the hope that these would be retrofitted to 1.6.1.
It was fixed in nginx 1.7.3.
So, I would just like to do if these empty response issues have been
addressed? It seems like a major stability concern.
You should use mainline version. SPDY fix isn’t a critical one, so it’s
unlikely to be merged in 1.6.
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are
at nginx.org.