Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x48La-006wFG-0E for pgsql-www@arkaria.postgresql.org; Wed, 09 Sep 2026 02:47:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x48LY-00B8En-34 for pgsql-www@arkaria.postgresql.org; Wed, 09 Sep 2026 02:47:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x48LY-00B8Ee-1h for pgsql-www@lists.postgresql.org; Wed, 09 Sep 2026 02:47:36 +0000 Received: from mail-pl1-x62a.google.com ([2607:f8b0:4864:20::62a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1x48LW-00000004hM7-1xov for pgsql-www@postgresql.org; Wed, 09 Sep 2026 02:47:35 +0000 Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-2db18e5cb56so51348045ad.0 for ; Tue, 08 Sep 2026 19:47:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1788922053; x=1789526853; darn=postgresql.org; h=user-agent:content-disposition:content-type:mime-version:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to :content-type; bh=xxF61c1CAAqm7Z5uImrdIALAvUNyrV0crpfX6454g3g=; b=IXI+gUi9kehfLT7LDI+lqeZieMUqHdmeRoL6YGMZbMfNKv6uXR/CUZTV/jbncvMKUY NixUpB7AA8F3MOIye4e9LPAqhC48K9SlZjvWEYA4gLpH525zoWQMDARtfQ06i+rjwVZ8 OgxJqtQPBLWpuFz96jcx4Gzwyzi2KyCcF6rj8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788922053; x=1789526853; h=user-agent:content-disposition:content-type:mime-version:message-id :subject:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to:content-type; bh=xxF61c1CAAqm7Z5uImrdIALAvUNyrV0crpfX6454g3g=; b=LMZEgWYJoUSiKQ794LoJJ4v/5ouCDsPDA52+B5IzCjxcImywvm+IgmwTutqmObT4uN vweZSiyFh9Yg+1bAyuio7pIxkEI832qLPZ5ugnaC0oer3dUuyfIogG0WYjrByPlD+pJh MNWwcDjQ6nT1oRw8f+Pz8gcwVkfE4Q+qCBMO1UJysCVI1ISw0piKewyKwO4w2ZOh8s0C HehAVMVCSpAqGFiz5XT2VQ+M6wxHfCUtRHardFOQ0ZVAFizsNdfJy14XtpAtJggEfmMV tfhODvW9k7jzRC/rYiBOcMTojVVLu0uKlUc681riagFQW/Gc6JPTne51e0zjKvoR78P3 qafQ== X-Gm-Message-State: AFuF++kH5QuZQWbXBdyolCVDWuMVSj/T0CjG6/lt3NIW+M/5w/pcPN+H WyW0uuwmcGRHdzl9d096XLxEyzdrByucMjtQxL9SV8fbByr/VgHhTuA6fVsX4+zJhmyfkG1cDWQ Yz5FvLw== X-Gm-Gg: AYBFou3fc4VzNEzBktO+xN8bVO6dFqPiaPCgMV/YRhsmY0FYgAgjHUvSvUwJdye8KCq VuGX5KwDHQlPqAzSBiLsXSRIrCDqvKsB4Xyv6ZEWUmcjuwlOhsR8EaGPtCUSP2xV+q+9KaaiJTh jYzJdQNER+zU/T1xYVFEQ8oaa70kL7A91hXJQVjI0l/+cYgL9g+4h1P+sySQQ4Kgz3hq+N9N/D4 d/NEHxP1jrjIsZA6Tc6z8nze72aP9qxsSil9G9AFo1WEEnsd2KdNOKQr6HdKwTrvYlBmxTLD4bv uuVnXOoVgCJb1LvDQtmrgRwH18TBjw277PkPK80MUUC9VOptckNISWailDflGSTslxkZcxgj9VX LRQvvZO3DlqwOzB61EiIGuqXV5LsCNzeHkm8E9+vLoSI8b603kcpqUAFa+Oq0iupf3EGndbg1pD +pAb/86jME5uZot9r545Ib1gmsQD6eAIrVdiCD54eWVho3ZLVIFahiVqz2ZIbsVwcdLAR94rjAD HrAJBkR08/+3QLyq8xo5lBLhyFXHsiUle4= X-Received: by 2002:a17:90a:1c81:b0:39b:3109:10ce with SMTP id 98e67ed59e1d1-39b310914e0mr30006391a91.16.1788922053265; Tue, 08 Sep 2026 19:47:33 -0700 (PDT) Received: from rfd.leadboat.com (c-73-15-160-255.hsd1.ca.comcast.net. [73.15.160.255]) by smtp.gmail.com with ESMTPSA id a92af1059eb24-143243767e1sm33804769c88.6.2026.09.08.19.47.31 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Sep 2026 19:47:32 -0700 (PDT) Date: Tue, 8 Sep 2026 19:47:29 -0700 From: Noah Misch To: pgsql-www@postgresql.org Subject: wiki login expiration Message-ID: <20260909024729.b1@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/2.3.0 (2026-01-25) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Can we make wiki logins persist for substantially longer? wiki.postgresql.org appears to require a new click on the "log in" link every hour or so. The cookie itself has a 30-day expiry, so I gather the server is expiring its side of the state faster. GPT thinks $wgObjectCacheSessionExpiry is the relevant mediawiki setting. Perhaps 30d (86400*30) is a reasonable setting? The new "log in" click usually doesn't require new credential entry, because the community login cookie is much longer-lived (>1wk). Still, it's an obstacle. The wiki's behavior of showing cached content to logged-out users makes this especially important. Visiting the open items page while logged-out may not show the last many hours of changes.