| Author |
Message |
   
David Matthews
Username: drmatthewsusa
Registered: N/A
| | Posted on Friday, Apr 3, 2009 - 22:19: | |
I need to explain the number in the count column to the requestors of investigations and want to do a reality check to see if I understand it correctly. In the Help it says that it is "The number of times the URL was accessed according to the log data". Is this an incremental number, meaning the same URL has been accessed that number of times since the log was started, or is it the number of times the URL was accessed in that one session (the date/time of that line)? The latter seems unlikely since this number can sometimes be quite large. TIA, David Matthews, CISSP, CISM CFI |
   
Jimmy Weg
Username: jw
Registered: 7-2006
| | Posted on Saturday, Apr 4, 2009 - 21:27: | |
The hits, in the context of an URL record and not with respect to a given tool, is interpreted based upon the index type: master, daily, weekly, and cache. The master hits number is visits to a site. Daily and weekly hits provide the same information, respective to the day and week. The cache count indicates the number of times that the file was retrieved from the cache. Note, however, that a number of 1 may be indicated where no hit count is available. You should be careful about counting, and the main history is the most reliable. |
   
David Matthews
Username: drmatthewsusa
Registered: N/A
| | Posted on Monday, Apr 6, 2009 - 17:50: | |
So, the number in the 'count' column in Trace reports is the cache count? If that is so, does that mean that the file has been retrieved that many times from cache in total (this is an incremental number)? Or is this a number of times it was retrieve from cache in this one session? Sorry if I'm being a little dense - I want to be sure I have this right. D |
   
Jimmy Weg
Username: jw
Registered: 7-2006
| | Posted on Monday, Apr 6, 2009 - 21:06: | |
It's incremental, in that it doesn't change between MSIE sessions. However, I've seen inconsistencies with this number, with resepct to how many times the resource was visited versus the number. I've gone to the same location twice, but have seen the cache count as perhaps 5 for a given jpg. |
|