Time to first byte 0.00 in Chrome over HTTPS


I notice that when testing with Chrome browser over HTTPS, there is a bug where 0.00 shows up as Time to First Byte. This happens often. WHat causes this? Any workaround to this?


Do you have sample results? If so can you open an issue on github with links?

Just did a quick test and it looks ok but there may some edge case somewhere: http://www.webpagetest.org/result/150903_BS_28f2eaa4d752ab21d364b4650e967ba7/