search

AnantLabs / speedtracer

Automatically exported from code.google.com/p/speedtracer
0 stars 0 forks source link

Request and Response Header not being captured #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Chrome version 7.0.503.0
The header in the network (resources) view are empty.

The version of Speed Tracer (check the chrome://extensions url)
0.17 and trunk

This looks like a Chromium bug as it works in early versions chrome with the 
same version of speedtracer.

Note: This is effects the integration with appstats.

Original issue reported on code.google.com by miller.garym on 30 Aug 2010 at 6:01

GoogleCodeExporter commented 9 years ago

Original comment by con...@google.com on 16 Nov 2010 at 5:54

GoogleCodeExporter commented 9 years ago 
I'm having the same issue with
Chrome 9.0.572.1
Speed Tracer (by Google) - Version: 0.18

on 

Mac OS X 10.6.5

Original comment by andrea.c...@gmail.com on 19 Nov 2010 at 6:08

GoogleCodeExporter commented 9 years ago 
I'm having the same issue with
Chrome 8.0.552.237
Speed Tracer (by Google) - Version: 0.19

on 

Mac OS X 10.5.8

Original comment by di...@fmpwizard.com on 27 Jan 2011 at 9:43

GoogleCodeExporter commented 9 years ago 
fixed at least by 10.0.648.6 dev

Original comment by con...@google.com on 28 Jan 2011 at 10:08

GoogleCodeExporter commented 9 years ago 
The current dev channel (11.0.696.12) appears to have broke this with identical 
symptoms. Is it helpful to open another ticket?

Original comment by adamsc@gmail.com on 16 Mar 2011 at 4:05

GoogleCodeExporter commented 9 years ago 
#5 i'll just reopen this one. thanks for letting us know.

Original comment by con...@google.com on 16 Mar 2011 at 4:09

GoogleCodeExporter commented 9 years ago 
Chrome Mac 13.0.782.4 dev  + Speedtracer 0.23, still no luck

Original comment by dom.guar...@gmail.com on 4 Jun 2011 at 12:23

GoogleCodeExporter commented 9 years ago 
Probably fixed in Dev channel.

Original comment by knor...@google.com on 21 Jun 2011 at 7:21

GoogleCodeExporter commented 9 years ago 
Indeed, this was fixed recently.

Response headers are not stored in the cache, so if an element is pulled from 
cache the Response Headers list is empty. This leads me to another thought: 
assuming the from cache code is now correct (and it appears to be from a 
cursory examination), we should color cached resources like we color redirects 
to call them out as special. In this case, they are a good kind of special.

Original comment by con...@google.com on 21 Jun 2011 at 7:33

GoogleCodeExporter commented 9 years ago

Original comment by knor...@google.com on 27 Jun 2011 at 4:23