From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Chuck Hallenbeck <chuckhallenbeck@gmail.com>,
Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] Signing into my Amazon account
Date: Sat, 6 Jan 2018 07:12:21 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801060711290.9659@debian.pulsar.com> (raw)
In-Reply-To: <20180105203532.GA30696@nautica>
Hi everyone,
Turns out I still have a problem signing into my Amazon account,
although it no longer segfaults.
The credentials that work correctly using windows fail to work using
edbrowse.
Those credenttials have been stable for several months, and I am
well-known to Amazon by virtue of my Amazon Echo device, which uses
the same credentials on my iPhone app., resulting in my receiving
occasional emails from Amazon.
I have captured a failed sign-in attempt with the edbrowse db level
set to 3, which seems to reveal two JS errors, and I hope someone
will take a look at it. It's above my paygrade, I'm afraid.
The file containing the failed signin is only about 3K, and can be
fount here:
www.panix.com/~chuxroom/signing-in.txt
Note the tilde following the slash in the address.
Chuck
--
Here In Northeast Ohio also, The Moon is Waning Gibbous (75% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Leslie's iPhone.
next prev parent reply other threads:[~2018-01-06 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 19:54 Chuck Hallenbeck
2018-01-05 20:35 ` Dominique Martinet
2018-01-05 20:53 ` Chuck Hallenbeck
2018-01-05 22:19 ` Kevin Carhart
2018-01-05 22:04 ` Karl Dahlke
2018-01-05 22:55 ` Kevin Carhart
2018-01-05 23:40 ` Chuck Hallenbeck
2018-01-06 12:12 ` Chuck Hallenbeck [this message]
2018-01-06 12:20 ` Dominique Martinet
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.1801060711290.9659@debian.pulsar.com \
--to=chuckhallenbeck@gmail.com \
--cc=asmadeus@codewreck.org \
--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).