| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: wiki login expiration |
| Date: | 2026-09-11 18:35:00 |
| Message-ID: | 20260911183500.ec@rfd.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Fri, Sep 11, 2026 at 12:28:32PM +0200, Álvaro Herrera wrote:
> On 2026-Sep-08, Noah Misch wrote:
> > 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?
>
> I changed this to 7 days; the documentation
> https://www.mediawiki.org/wiki/Manual:$wgObjectCacheSessionExpiry
> explains that the logout occurs if you're _inactive_ during that period,
> so this should be ergonomic enough for most people, I hope. I'm not
> completely sure if the service restart I did is enough for the setting
> to take.
Thanks. Since your email, I've had the wiki login expire twice more in the
same browser, so I don't think the change has taken effect yet.
I agree logout after 7d inactive is plenty generous.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2026-09-12 08:55:36 | Re: [PATCH] pgarchives: Fix crash when receiving a request with an incorrect If-Modified-Since header |
| Previous Message | Magnus Hagander | 2026-09-11 15:59:14 | Re: archives frequently do not load today's messages |