edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] possible Referer issue
Date: Tue, 9 Jan 2018 21:55:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1801092154320.24645@debian.pulsar.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1801091428200.18256@carhart.net>

Hi Kevin,

I looked at how one gets from the Amazon opening screen to the
sign-in screen by using the capital A command on line 11, and it's
not pretty. I'm not up to tackling that shortcut myself.

About cookies, in my debugging output I see references to expired
cookies, which seems strange.  But I have another concern:

It appears that issuing the db5 command and diverting the resulting
output to a log file changes the behavior of edbrowse.  Let's consider
two cases, first with db1, which is my default in the rcfile.
and second with db5, and the command to redirect  output to a log
file before opening amazon.com.

Cases 1 and 2: Open edbrowse and get a prompt.

Case 2 only: enter db5, then db>/tmp/log

Cases 1 and 2. Enter e www.amazon.com, and get the raw html size,
usually about 400000,

In case 1, but not case 2, we soon get the rendered size, a much
smaller number, and the opening screen is ready to be used.

In case 2, the buffer contains only the raw html, and we must type
the b command to render it, and only then do we see the smaller size
and can use the opening screen.

In both case 1 and case 2, we go to line 11, which contains five
links, we enter g2 to get to the sign-in screen, where we enter our
ID and Password.

For Case 1 only, we press submit and are taken to a new screen
resembling the sign-in screen, except for the messages near the top
saying "An Error Has Occurred" and "Enter a valid email address or
phone number" or some such wording.

The ID you previously typed is shown, but the password field is empty.
That was for case 1 only.

For case 2, pressing the submit button on the sign-in page causes
a segfault.

I would think the program behavior should not be changed by activating
a higher debug level, but the above is consistent and reproducible, and
makes me wonder how reliable the data in the resulting log file are.

Chuck



-- 
Here In Northeast Ohio also, The Moon is Waning Crescent (38% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Camille's iPhone.

      reply	other threads:[~2018-01-10  2:52 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
2018-01-10  2:55       ` Chuck Hallenbeck [this message]

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.DEB.2.21.1801092154320.24645@debian.pulsar.com \
    --to=chuckhallenbeck@gmail.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    --cc=kevin@carhart.net \
    /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).