Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > Similar errors might as well be a result of e.g. > network connectivity > problems. It's hard to say anything without > detailed inspection > of a failure on the client side. > We've been able to replicate once in a VM running Win 7 w/ Chrome. > There is at least sevby bpiraeus - Nginx Mailing List - English
I stumbled across this this morning after talking with some co-workers about what we're seeing http://code.google.com/p/chromium/issues/detail?id=85229 I'm wondering if someone @ MS decided IE9 would benefit from the same speculative pre-connect sockets. If we strip out anything that's not IE9/Chrome we're left with a pretty small subset of 'other browsers' which I'm leaning towards considerby bpiraeus - Nginx Mailing List - English
The problem with that diagnosis, is that in this case, it's actually causing failures on the client side. The client in question has a flash game which pulls some amount of data over https, when these sessions time out and hand out a 408, it causes the game itself to barf up a lung. Additionally after pulling 12 hours of logs and doing UA matching, while Chrome on Win7 base seems to be the major pby bpiraeus - Nginx Mailing List - English
I should note, I've also tried various revisions of nginx, the debug was taken using 1.1.19 w/ the following configure options --with-http_ssl_module --with-http_stub_status_module --with-ipv6 --with-pcre --with-debug --with-openssl=/usr/local/src/openssl-1.0.1by bpiraeus - Nginx Mailing List - English
While debugging for a client, we found that we're seeing significant numbers of 408s being generated for SSL connections. It seems to be MOSTLY Chrome on a Windows 7 base with some MSIE 9.0 (also on Win 7) as user agents go, and at this point I'm completely stumped. We've tried disabling session cache, upping timeout values, enabling/disabling keepalives, nothing seems to stem the steady flow of tby bpiraeus - Nginx Mailing List - English
I've some poking around and I'm not seeing anything relevant so I'm wondering if anyone has found a feasible method of pointing nginx at a remote keystore for fetching certificates on startup/reload? Conceptually this is for PCI compliance and keeps the certificates from ever being anywhere except encyrpted on the wire or in memory.by bpiraeus - How to...