Null ETag found when trying to serve resource from cache

Feb 4, 2010 at 10:00 AM


We are currently seeing an issue when trying to serve a resource from the server cache, where in certain circumstances which we have not been able to identify, the etag is returned as null from the server cache. This is happening even though the response data is still in the server cache. Have you seen this issue before?


Feb 4, 2010 at 5:49 PM


Been looking into the problem, and I think that you need to make the data cache item dependant on the etag cache item, as at the moment, if the etag is flushed from the cache, the data will remain, which results in the problem we are seeing.

What do you think?



Feb 5, 2010 at 10:38 AM

Hi Brian,

Thanks a lot for reporting the issue and submitting a patch.  I have applied your patch in the latest code commit.