navigation error - broken webpagetest

Support
1

Hi,

I’ve been trying to test our site using London chrome location and every time for the last day or so it’s been giving a navigation error. Looking at the waterfall it goes to http://www.gstatic.com/generate_204 and then stops. Doesn’t even try the url.

Here you can see: Dropbox - Screenshot 2014-06-12 10.18.48.png - Simplify your life

2

Are you still seeing issues? I just tried a test and it appears to be working ok: http://www.webpagetest.org/result/140616_YS_c7db63f3023c82170806caf1ccf21c1d/

3

Still seeing the error: http://www.webpagetest.org/result/140617_QX_HYS/

2014/06/17 12:53:07 - Test Created
2014/06/17 12:53:16 - Starting test (initiated by tester WWW-84.45.55.126)
2014/06/17 12:53:16 - Run 1 assigned to WWW-84.45.55.126
2014/06/17 12:54:07 - Test Run Complete. Run: 1, Cached: 0, Done: , Tester: WWW-84.45.55.126
2014/06/17 12:54:07 - Test Run Complete. Run: 1, Cached: 1, Done: , Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:54:07 - Test Run Complete. Run: 1, Cached: 1, Done: 1, Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:54:40 - Run 2 assigned to WWW-84.45.55.126
2014/06/17 12:55:32 - Test Run Complete. Run: 2, Cached: 0, Done: , Tester: WWW-84.45.55.126
2014/06/17 12:55:32 - Test Run Complete. Run: 2, Cached: 1, Done: , Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:55:32 - Test Run Complete. Run: 2, Cached: 1, Done: 1, Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:55:59 - Run 3 assigned to WWW-84.45.55.126
2014/06/17 12:56:51 - Test Run Complete. Run: 3, Cached: 0, Done: , Tester: WWW-84.45.55.126
2014/06/17 12:56:51 - Test Run Complete. Run: 3, Cached: 1, Done: , Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:56:51 - Test Run Complete. Run: 3, Cached: 1, Done: 1, Tester: WWW-84.45.55.126, Test Run Error: “Skipped repeat view, first view failed: Test run failed with result code 12999”
2014/06/17 12:56:51 - Test Complete
2014/06/17 12:56:51 - Test post-processing complete

Your one isn’t a https test, perhaps thats what’s broken?
[hr]
Trying to test: Lady's Mile Holiday Park, Dawlish - Updated prices - Pitchup®

4

another strange thing, when I test a http url, like http://www.pitchup.com/ it works, but in the result we see the http connect response with a redirect (normal and correct) but then takes 18 seconds to even make an attempt on the https link

http://www.webpagetest.org/result/140618_7A_JAH/1/details/

5

Managed to reproduce it with timeline and tracing enabled: http://www.webpagetest.org/result/140618_M1_a5136bd6028365445bc9d77590613875/#run4

The timeline makes it look like chrome issued the request for the https redirected page right away but it took 18s before getting the response (but from the timeline view that includes both the SSL negotiation and the first byte time).

The trace looks like it took 16 seconds before the request itself was actually sent so it looks like it’s probably somewhere in the SSL negotiation. re-running now with netlog and tcpdump to see if either of them provide more useful information.

6

Netlog was pretty much worthless but looking at the tcpdump I see a bunch of traffic for digicert OCSP and CRL checking. (here is a test with the tcpdump if you want to pour through it: http://www.webpagetest.org/result/140618_0S_6a0746326d23d1f80a7baefc05ecb275/ )

As best as I can tell:

  • (10 second mark) 2 SSL connections get started right away
  • there is some traffic to ssl.gstatic.com for ~1 second (can’t tell if that’s related or just background browser stuff)
  • There are some WPAD queries going out (wouldn’t expect them since we run Chrome with proxy disabled)
  • (13 second mark) ocsp.digicert.com lookup
  • (18 second mark) crl3.digicert.com lookup
  • (24 second mark) crl4.digicert.com lookup
  • (24 second mark) SSL connection to server is re-opened (presumably previous one timed out)

The bizarre thing is that I don’t see any attempt to actually connect to the address for ocsp. and crl3.

It looks like you have an EV cert from digicert so Chrome will do OCSL and/or CRL verification for it (for regular certs it skips the online verification) and it looks like that is where the bulk of the time is going. Still not sure exactly what is broken with the cert verification though.

7

strange, chrome has disabled ocsp by default (has it been turned back on)

anyways, i’ve configued oscp stapling so it shouldn’t need to do those checks and now going to test again

thanks for your debugging help

8

Chrome only disables OCSP for non-EV certs.