We can see the timings all suggest that this isn't a cached entry, as does the _transferSize field. So maybe _transferSize is the only way of determining if a Chrome HTTP/2 entry is cached or not? The existing code tries to use a greater-than-zero bodySize as an indication of cached or not, but it is set to -1 here.
The cache object is empty, and so this is of no help.
See the request for https://www.google.co.uk/ is grey, as only a cached entry should be coloured. And see the connection bar has all the hallmarks of a non-cached request.
Looks like HTTP/2 might be involved.
Sample snippets of an entry below.
We can see the
timings
all suggest that this isn't a cached entry, as does the_transferSize
field. So maybe_transferSize
is the only way of determining if a Chrome HTTP/2 entry is cached or not? The existing code tries to use a greater-than-zerobodySize
as an indication of cached or not, but it is set to-1
here.The
cache
object is empty, and so this is of no help.See the request for
https://www.google.co.uk/
is grey, as only a cached entry should be coloured. And see the connection bar has all the hallmarks of a non-cached request.Whereas Firefox 60 gives a
>0
bodySize
:More complete version of the Chrome entry above: