From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] possible Referer issue
Date: Tue, 9 Jan 2018 14:58:30 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1801091428200.18256@carhart.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1801090751310.2061@debian.pulsar.com>
Thanks, Chuck! Yes.. breaking down multiple factors is a problem.. not
knowing which of these point of divergence is the important one. That
said, I suspect the cookies, and the session-token cookie in particular.
There needs to be a conversation where it is received, sent back out, and
if the site gives you a new one, you send that one back in your next
request. If I understand what I'm reading, this isn't happening in
amazon.chuck.5 and in my failed attempts, and it does happen in
amazon.wendy.5.
The only references to session-token in amazon.chuck.5 are outgoing.
It does not appear in any Response. I bet this is important. Of
course I had a totally wrong hypothesis earlier so I could be wrong.
As a side suggestion, I think we can load the login-and-password screen on
first visit, and maybe save some hops and some bloat.
Technically we should be able to open a new edbrowse and 'b' the
login-and-password screen's URL from the getgo. I don't think we have to
visit the homepage and 'g' a link first. This would make the HTTP
conversations shorter.
On Tue, 9 Jan 2018, Chuck Hallenbeck wrote:
> Hi Kevin,
>
> I have amazon.wendy.5 here too, and have posted two db5 runs of my own failed
> logins. I used grep to search for prepopulatedLoginID in all three files, and
> found this:
>
> $ grep -c prepopulatedLoginId amazon*
> amazon.chuck.5:0
> amazon.wendy.5:16
> $ grep -c prepopulatedLoginId signing-in.txt 1
>
>
> My outputs are available from www.panix.com/~chuxroom/signing-in.txt
> and www.panix.com/~chuxroom/amazon.chuck.5
>
> However, the file "signing-in.txt" was generated before the segfault was
> detected and fixed, so the amazon.chuck.5 is probably a closer source.
>
> Running here on Debian Sid, edbrowse 3.7.1, curl 7.57.0.
>
> Chuck
>
>
> --
> Here In Northeast Ohio also, The Moon is Waning Crescent (44% of Full)
> When your only tool is a hammer, everything looks like a nail.
> Sent from Sergio's iPhone.
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2018-01-09 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:11 [Edbrowse-dev] the amazon saga Chuck Hallenbeck
2018-01-09 9:22 ` [Edbrowse-dev] possible Referer issue Kevin Carhart
2018-01-09 13:01 ` Chuck Hallenbeck
2018-01-09 22:58 ` Kevin Carhart [this message]
2018-01-10 2:55 ` Chuck Hallenbeck
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=alpine.LRH.2.03.1801091428200.18256@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
/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).