On Tue, 19 Oct 2010 22:29:29 +0800, mohd hafiz <bmhafiz@xxxxxxxxx> wrote: >> >> 2.6 requires building Squid with the "null" storage type. >> >> Then configuring with "cache_dir null /tmp". >> IMPORTANT: do not use /dev/null. There are important run-time state >> files >> stored in the top of cache_dir by older squid. > so in my squid.conf: > cache_dir null/tmp (note the space: cache_dir null /tmp) > when this is done, i will able to see all tcp_miss in the access.log right? I forgot this bit as well sorry. Needs to be the only "cache" allow/deny line. cache deny all That will discard form the memory storage as well. >> >> If cache_dir are all removed Squid 2.x allocate a 100MB space in >> /var/spool >> or /var/cache depending on your OS. >> > what will be store in the new allocated space(/var/cache or /var/spool) ? Any cacheble reply objects. Same as if you set a working cache_dir entry in squid.conf. > >> Turn of "offline_mode" if you have it set in squid.conf. Despite the >> name, >> it only causes aggressive caching to be done. >> > i have disable the offline_mode. Does squid cache DNS lookup? can > squid set to not cache dns? i want browser always perform new dns > lookup > instead using cached dns in squid. How DNS operate/interact with squid > make me confused. When a browser is configured to use a proxy it *never* performs DNS for traffic sent there. The proxy does it all instead. When a browser is not aware of the proxy (NAT interception) it performs its own DNS which gets discarded again as the packets enter the proxy. DNS inside Squid follows required specifications. Yes it caches DNS, for the times required by individual IPs and domains. If you don't understand any of it *don't touch*. Preventing caching of these will result in your users spending very large amounts of time waiting for pages to arrive. Amos
