Firefox not using cached copy of file after 304?

OK - I got to the bottom of this problem. As ever - the answer was staring me in the face!

OK - I got to the bottom of this problem. As ever - the answer was staring me in the face! The problem was not with the caching behaviour at all.

Another part of the system was sporadically failing and writing out a zero length file - which was being cached by Firefox. So when Firefox sent a conditional request to the server and received it's 304/Not Modified, it dutifully went off and used the corrupt zero length version of the file that it found in its cache. All the signs were there for me to see - it just took a bit of time to get there :) Thanks all, for your comments and suggestions.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.