Description of issue
We have a web server that is serving static assets. We are experiencing a problem where after you browse around some of the http requests get stuck in the "pending" state. In the chrome inspector the response headers do come back, but the requests don't time out and they look like they are downloading. In the timeline view the "Waiting (ttfb)" is the last item filled out (400ms for example), and then there is a note "CAUTION: request is not finished yet!"
This issue seems limited to chrome, and when the site is being run https. We can't reproduce on safari, ff, ie, and we can't reproduce if https is off.
Repro. steps taken
- open chrome incognito
- open inspector tools > net tab
- navigate to site
- usually the first page and all of it's requests finish
- browse to another page
- unexpected behavior: parts of the page don't load; xhr requests for .html files, and jpg images typically. When inspected in chrome's net tab they say "pending"
- after following the steps above, if you open the "pending" request in a new tab the tab "spins"
- if you close the first tab, the second tab with the "pending" url resolves, this lead us to look into keep alives and timeouts, but to no avail.
- This full issue can sometimes present itself on the very first request as well (document)
- frontend is angularjs, accessed via chrome other browsers don't seem to have this issue
- server is run https, wildcard cert ( *.domain.com )
nginx version 1.9.3
# some variables we've tweaked worker_processes 4; worker_connections 4000; keepalive_timeout 15; client_body_timeout 12; gzip on
nginx logs don't complain about anything
- the cpu / ram never get anywhere close to maxxing out when there is load on the server
- the response headers include; etag, gzip, content-type, date, last-modified, server, status (200), strict-transport-security:max-age=604800 ...
- changing chrome's "disable cache" checkbox doesn't seem to effect things
- we've experienced this on man chrome browsers on different computers. I'm running 44.0 64bit on max
Based on these issues the bug feels like some type of server configuration issue, we don't think it is cert related, but the fact that it only impacts chrome is really odd.