Hmm, thanks - I'll take a look.
I know I had a problem where IE 11 wasn't reading responses so everything showed up as a -2 so it was on my list to look at (like this:
http://www.webpagetest.org/result/140206...1/details/ ). I'll take a crack at it today. Looks like they probably just evolved how they read/write to the sockets and schannel and I need to adapt the hooking.
Oh, any chance that that page is SPDY? IE 11 introduced SPDY support and the WPT agent doesn't have a SPDY decoder yet (been on my todo list for a while).
(02-07-2014 05:54 AM)pmeenan Wrote: [ -> ]Oh, any chance that that page is SPDY? IE 11 introduced SPDY support and the WPT agent doesn't have a SPDY decoder yet (been on my todo list for a while).
I believe the site is not SPDY
http://spdycheck.org/#developer.amazon.com
It is strange that IE11 fails for this site but works on others.
Can the http compression play a role?
Hi
I had the same problem with IE11 and I saw on github that you fixed the problem :
https://github.com/WPO-Foundation/webpag...261940d03f
But the 2.13 version was released 4 months ago and seems to not contain the fix.
Do you plan to make a new release with this fix soon ?
(03-07-2014 08:00 AM)pmeenan Wrote: [ -> ]Hopefully next week as I clean up a few other nagging issues. That said, you can always update the agents separate from the www releases (and I recommend it): https://sites.google.com/a/webpagetest.o...est-Agents
Thanks for the update
I installed the new version and they seem to work fine, except maybe a problem with chrome but I'll check that further.
Why the reco ?