sagenb: notebook cookies #8249
Description
This is a followup to #6353. That ticket improved cookie naming a bit. However, it appears to be not enough.
On Thu, Feb 11, 2010 at 7:21 PM, Marshall Hampton <> wrote:
> Just for the record, this has happened to me quite a bit recently.
>
> I use a lot of different sage servers, often running different
> versions, so I don't usually report this kind of stuff since I think I
> am something of an extreme case. But most of the servers I use are
> now running 4.3.2 and I am pretty sure I have seen the cookie message
> more than before.
>
Here's the relevant ticket I was remembering:
https://github.com/sagemath/sage-prod/issues/6353
It is definitely in sage-4.3.2 (since it is merged into sagenb-0.7.4).
Looking at that patch show that:
(1) it addresses a related issue,
(2) it might not solve the issue we're discussing, since it merely includes the *port* in the cookie name -- some unique id for the notebook (e.g., the URL or something else) is maybe also needed to fix the problem we're discussing.
So somebody should look at ticket 6353, see if a small modification of it would give a real fix, and make said modification. Alex Leone: this would be a good project for you, if you're looking for something to do on the notebook.
-- William
See sage-support.
CC: @sagetrac-acleone @qed777 @sagetrac-mhampton
Component: notebook
Author: Mitesh Patel
Reviewer: Alex Leone, Tim Dumol
Merged: sagenb-0.8
Issue created by migration from https://trac.sagemath.org/ticket/8249