I emailed you detailed info.
The symptom of the bug would be, that data of one video-request will receive
the storage key of the request for another video, and vice versa.
This can only occur, when you have 2 or more users accessing yt the same
time.
Or one user watching yt in 2 browser windows simultaneously.
So, the more users you have active, the higher the probability, that it
might show up.
I also sent you a suggestion, how to reduce the probability of the bug to
show up. Unfortunately, I do not see the chance for a fool-proof solution.
Unless, the rewriter has access to the header data of the GET.
AFAIK, this is not possible.
-- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Re-squid-3-Head-storeid-tp4659552p4659585.html Sent from the Squid - Users mailing list archive at Nabble.com.Received on Sun Apr 21 2013 - 08:38:30 MDT
This archive was generated by hypermail 2.2.0 : Sun Apr 21 2013 - 12:00:04 MDT