Geff wrote:
I'd also like to say that this issue doesn't just affect the 'no-cache' case but it also seems to affect the case when the cache decides it needs to revalidate a resource with the original server. The 'no-cache' method is just a convenient way to demonstrate the problem and force the cache to try to revalidate the resource.
From what I understand this is caused by some buggy versions of IIS v5 which send Content-Length: 0 along with 304 responses.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
