From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out.smtp-auth.no-ip.com (out.smtp-auth.no-ip.com [8.23.224.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id BADA477C8C for ; Sat, 19 Dec 2015 15:07:18 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 38F1F400C4B; Sat, 19 Dec 2015 15:07:20 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id tBJN7J84030431; Sat, 19 Dec 2015 15:07:19 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id tBJN7Iub030423; Sat, 19 Dec 2015 15:07:19 -0800 Date: Sat, 19 Dec 2015 15:07:18 -0800 (PST) From: Kevin Carhart To: Karl Dahlke cc: Edbrowse-dev@lists.the-brannons.com In-Reply-To: <20151119082426.eklhad@comcast.net> Message-ID: References: <20151218202619.GA5465@acer.attlocal.net> <20151119082426.eklhad@comcast.net> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Edbrowse-dev] Accessing fastmail X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2015 23:07:18 -0000 This is interesting.. yes, so we just fixed the problem with the onsubmit, meaning (thinking out loud) that in spite of the fact that the onsubmit doesn't have a return value, the appropriate routine in ebjs (run_function_bool) now defaults to true rather than defaulting to false if it bails out early. So we did that even though Karl said "this could have ramifications beyond just this one scenario." I guess maybe it's a rare case that if it's a function that is supposed to return true or false, that they would just leave it off and not return anything. So that's the background. Hopefully it's pretty rare and/or this is actually the right thing to do broadly. > So I imagine this session cookie is not set properly in js, > back to edbrowse, and into curl, or some such. > The cookie code posted seems incompatible with > what the document.cookie settter function expects. > > use_classic=1;max-age=604800;expires=Fri, 25 Dec 2015 01:52:50GMT;path=/ > > All run together no spaces. Indeed - when I play along, try to delete an email and I get the same session error that Chuck gets, I then examined document.cookie using jdb: jdb document.cookie use_classic=1 So that's confirmation that the cookie is being truncated. (I'm happy about jdb mode! It's helpful for getting a quick answer inline.) Knowing this, what do we do? Kevin