When running a test on https://naturebox.com/:
Firefox - http://www.webpagetest.org/result/140430_EZ_FPA/1/details/
Chrome - http://www.webpagetest.org/result/140430_WN_FPX/1/details/
As you can see, in Firefox it seems that the waterfall is missing the first half of the resources.
SPDY decode hasn’t been implemented for Firefox or IE 11 yet so you won’t be able to see those resources. Should have it fixed in the next month or so.
What’s the status on this issue? and if it’s not being pursued, what steps do I need to take to start working on it?
Still high on my list but keeps getting bumped down as other things come in. If you want to take a crack at it you’ll need Visual Studio 2010 to build the test agent.
The code for wpthook (the part that does the network intercepting) is here: https://github.com/WPO-Foundation/webpagetest/tree/master/agent/wpthook
Specifically track_sockets.cc, DataOut() and DataIn().
I was going to llok at just using spdylay to do the actual decoding and converting to http: https://github.com/tatsuhiro-t/spdylay so it might not be that difficult. I’m not sure if spdylay supports http2 though which a lot of browsers are starting to enable.
Thanks, I’ll try my best. Could you explain what the issue is exactly though? I have a general understanding of wpthook and the spdy protocol, but I’m still at a loss on why it works on Chrome but not on Firefox or IE.
For Chrome we don’t have access to the decrypted socket stream so we use an extension API for all https requests (and SPDY wors as a result of that). There is no protocol-level decoding going on for Chrome right now.
For Firefox and IE we can actually get the raw decrypted streams so we should actually be able to get much better data than we get from Chrome. We use it for https today but there’s currently nothing that decodes spdy streams of data.