From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Session timeout on commitfest.postgresql.org |
Date: | 2010-08-10 15:22:23 |
Message-ID: | 668.1281453743@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> $SUBJECT seems to be less than 12 hours, which is annoyingly
>> short. I don't see a good reason why I should have to log in
>> again every morning. I could see expiring the cookie in a week or
>> so, or tying it to a particular IP address, but this is just
>> getting in the way.
> Could it be a firewall doing that to you?
Don't see how a firewall could affect cookies. Possibly this is a
browser-specific issue, though. I'm using current-rev Safari on a Mac.
I notice it shows the commitfest cookie as having no particular
expiration time, which may mean that some Apple-specific expiration
policy gets applied. But on the other hand, when I got prompted to
log in this morning, I checked the cookie list and there was such a
cookie there already --- so it wasn't that the browser had just dropped
it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Otto | 2010-08-10 15:23:02 | Re: patch for contrib/isn |
Previous Message | Tom Lane | 2010-08-10 15:08:28 | Re: host name support in pg_hba.conf |