Speed Tracer shows Cached files as Not-Cached in Network tab about speedtracer

[GoogleCodeExporter]

Issue 21 has been merged into this issue.

Original comment by [email protected] on 11 Jun 2010 at 3:06

[GoogleCodeExporter]

Original comment by [email protected] on 11 Jun 2010 at 4:21

[GoogleCodeExporter]

I'm not seeing this exact description, but something is up: I see the actual 
requests go across the wire for resources that are definitely cached. 
Potentially a chrome bug...need to investigate some more.

Original comment by [email protected] on 11 Jun 2010 at 11:15

• Changed state: Accepted

[GoogleCodeExporter]

Interestingly, a trunk~week build of Chromium/Webkit doesn't exhibit this 
behavior. Looks like it has been fixed upstream, but I can't find the relevant 
issue report at the moment. 

Original comment by [email protected] on 11 Jun 2010 at 11:29

[GoogleCodeExporter]

related chromium bug:

http://code.google.com/p/chromium/issues/detail?id=44867

Original comment by [email protected] on 14 Jun 2010 at 3:26

[GoogleCodeExporter]

I've experienced the same problem on Chrome 6.0.458.1 dev.

Enclosed is the extract from the Apache access log file. It shows that the 
second time, the cached java script files are no refetched.
The speedsaver output howevers reports as if they were fetched.

Original comment by [email protected] on 15 Jul 2010 at 9:08

Attachments:

• other_vhosts_access.log
• speedtracer.zip

[GoogleCodeExporter]

Original comment by [email protected] on 21 Jun 2011 at 7:16

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Marking as fixed. I can't reproduce.

Original comment by [email protected] on 23 Jun 2011 at 8:17

• Changed state: Fixed