Incorrect content length

If I read this correctly, storeCheckSwapable() should prevent squid from
caching any object where the content-length differs from the length of
the actual object...

Or is that only checked when it comes to swapping hot-cache items into
disk-storage?

I'm looking at some broken objects now, and wondering why they were
TCP_HITs, when I figure the cache should have discarded them as
incomplete.

D
Received on Sun Mar 29 1998 - 21:30:23 MST