From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] document.cookie is fucked up
Date: Mon, 02 Nov 2020 03:01:48 -0500 [thread overview]
Message-ID: <20201002030148.eklhad@comcast.net> (raw)
Are you high? Are you completely baked?
This is a problem when no one is checking everything I write.
This has been wrong for years.
It's a wonder websites worked as well as they did.
edbrowse site1 site2
These should have cookies, or at least one of them anyways, they should present different cookies.
In either session, e1 or e2, jump into jdb.
document.cookie
It will always show you the cookies of the second site, never the first.
When the first site came up it had the right cookies, and maybe that's why a lot of things worked,
then the second site has its cookies but then those are the cookies you get; always the last cookies.
The stupid line of code,
jseng-duk.c 1253
As though there is one copy of cookies across all sessions and windows of edbrowse.
Now I have to think of a clever way to fix it, that isn't too gross.
I found this while converting stuff to mozjs c++, it forces me to read through it again,
and I got to that line and freaked out.
Then I ran the test as above on two websites, and sure nuff.
Karl Dahlke
reply other threads:[~2020-11-02 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201002030148.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).