Getting squid-2.3.stable3 to have cache hits

Hi,

With squid, should the second of two identical consecutive http
requests usually be cached?

That's not the behaviour I'm getting and I'm having trouble
figuring out why. In fact I can't seem to get a TCP_HIT at all
in the log file.

Eg from access.log, why is the second of these getting TCP_MISS?
960929245.326 1701 127.0.0.1 TCP_MISS/200 6191 GET http://www.aaa.net.au/greenleaf/ - DIRECT/www.aaa.net.au text/html
960929254.240 977 127.0.0.1 TCP_MISS/200 6191 GET http://www.aaa.net.au/greenleaf/ - DIRECT/www.aaa.net.au text/html

I've downloaded squid-2.3.stable3, built with default options
on linux Redhat 6, modified the squid.conf as follows:

47a48,49
> http_port localhost:3128
> http_port 192.168.1.1:3128
463c465
< #cache_dir ufs /usr/local/squid/cache 100 16 256

---
> cache_dir ufs /var/spool/squid 100 16 256
1204c1206
< http_access deny all
---
> http_access allow all
1284a1287
> cache_effective_group nobody
Then ran:
    /usr/local/squid/bin/squid -z
    /usr/local/squid/bin/squid
--
Regards,
-- Dave Campbell
David Campbell - david@pastornet.net.au Brisbane, Queensland, Australia
Director, Greenleaf Systems Pty Ltd, +61 7 3216 6015