On Thu, Feb 11, 2010 at 7:21 PM, Marshall Hampton <hampto...@gmail.com> 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:
http://trac.sagemath.org/sage_trac/ticket/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. I've opened a ticket:
http://trac.sagemath.org/sage_trac/ticket/8249
-- William
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
