No unfortunately, but I have since filed a bug in trac: http://trac.nginx.org/nginx/ticket/428by spdyg - Nginx Mailing List - English
David Gwynne Wrote: ------------------------------------------------------- > i am also experiencing this problem running 1.4.2. Hi David. The response I got from my Valentin off-list was that there is a known incompatibility with SPDY and proxy cache, due to the way proxy cache will kill the connection to prevent it sending the body response (but before it has had a chance to finish dealby spdyg - Nginx Mailing List - English
Reading the docs on nginx.org and searching around, it seems there's no consensus on how we should configure gzip_buffers. Some guides say that the total buffer needs to be greater than any file you want to gzip, or it will either not gzip the file or truncate it (I'm sure this is not true though!). Other guides suggest arbitrary values. I guess I have a couple of questions to clear up thisby spdyg - Nginx Mailing List - English
Do you have SPDY enabled? I have experienced issues with SPDY, upstream keepalive and proxy_cache together. Ended up having to turn off SPDY.by spdyg - Nginx Mailing List - English
Thanks Valentin. I have emailed you (off-list) some debug logs / screenshots.by spdyg - Nginx Mailing List - English
No there's nothing in the error log. Access log shows 304's for all requests that failed.by spdyg - Nginx Mailing List - English
Hi guys, So perhaps I shouldn't have reused my existing topic and confused things, sorry! I only did so because the symptom is exactly the same as the issue I originally reported (SOME static content served from proxy cache occasionally doesn't make it to Firefox when using SPDY). If you disable either SPDY or the proxy cache the problem stops happening. The originally reported problem sby spdyg - Nginx Mailing List - English
I posted this query back in December: http://forum.nginx.org/read.php?2,233497 And the issue was fixed shortly afterwards in the 1.3.x branch. I'm now seeing the same issue again (static items coming from proxy cache + SPDY not displaying). However this time, the log does not show 499 error anymore.. it just shows successful 304. However, looking at firefox web console, the first fewby spdyg - Nginx Mailing List - English
Hi there, I have been piloting the SPDY patch on a separate web server pointing to an existing HTTP backend. With just myself using this pilot web server, occasionally static resources such as css or images are not loading in Firefox (usually when pressing F5 to reload a page) Have done a bit of digging and have learnt this so far: When issue occurs in Firefox, access log is showing 49by spdyg - Nginx Mailing List - English