From bf4c2fb7d6407e37189d6d473b566c4fa021dd4a Mon Sep 17 00:00:00 2001 From: Tim Starling Date: Tue, 12 Mar 2013 11:32:54 +1100 Subject: [PATCH] Rewrite user_touched comment, since apparently it is not clear enough Change-Id: Ib993e5a6dc56963e9afbbdc2ada77762e1594f0b --- maintenance/tables.sql | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/maintenance/tables.sql b/maintenance/tables.sql index 97d6ff20f7..a9177838fb 100644 --- a/maintenance/tables.sql +++ b/maintenance/tables.sql @@ -86,10 +86,12 @@ CREATE TABLE /*_*/user ( -- Same with passwords. user_email tinytext NOT NULL, - -- This is a timestamp which is updated when a user - -- logs in, logs out, changes preferences, or performs - -- some other action requiring HTML cache invalidation - -- to ensure that the UI is updated. + -- If the browser sends an If-Modified-Since header, a 304 response is + -- suppressed if the value in this field for the current user is later than + -- the value in the IMS header. That is, this field is an invalidation timestamp + -- for the browser cache of logged-in users. Among other things, it is used + -- to prevent pages generated for a previously logged in user from being + -- displayed after a session expiry followed by a fresh login. user_touched binary(14) NOT NULL default '', -- A pseudorandomly generated value that is stored in -- 2.20.1