Yeah, I need to figure out where in the code that default is set. The requests are probably SPDY over SSL which is something that the Chrome agent can’t decode yet. They aren’t errors, I just don’t have visibility into the actual requests (it’s something we are working on).
SPDY has been in production for well over a year. Most HTTPS requests to Google from Chrome uses SPDY. Chrome has had support for it for quite a while as well. What “I” don’t have yet is code in WebPagetest to decode SPDY streams and deconstruct the individual requests.
I noticed this for my Website and spent hours going through the code for my site to check if there was an errant JS library making a weird SSL connection to Google. Then I thought of checking Facebook (BTW, FB is not my site, I am not Zuck from two locations:
Notice that requests 14 and 16 in their waterfall view are SSL connections to IP addresses 126.96.36.199 and 188.8.131.52 respectively. These IP addresses are owned by Google, and the SSL connections timeout.