NOVM access.log differences?

I noticed when previously an TCP_IMS_HIT in 1.1.10 now shows up as an
TCP_IMS_MISS in the 1.NOVM.10 version?

I see that in both cases there was no need to get the file externally
yet one says a "MISS" with data sent to the browser and the other a "HIT"
(not modified 304)

I'm just curious as to what effect it has on log analysis tools that
use the TCP_IMS_X when the logic has reversed? Should they use the
Hierarchy field to determine the effectiveness (hit rate) of the cache?

Or did I "MISS" something ;)

1.NOVM.10:
TCP_IMS_MISS/200 8301 GET http://www.yahoo.com/ - NONE/- text/html

1.1.10:
TCP_IMS_HIT/304 122 GET http://www.yahoo.com/ - NONE/- -

-- 
Kim Lee _______________________    o    _          _--_|\   Z I P  S y d n e y
Zip Guy kim@zip.com.au        /____|___|_)________/______\____________________
voice 92-704-777                       |          \_.--._*  V i r t u a l l y
modem 92-477-288 join us for Quakeworld  www.zip.com.au v      the best! :)