From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com, baggett@Colorado.EDU
Subject: Re: [Edbrowse-dev] Continuing Amazon issue
Date: Sun, 7 Jan 2018 20:16:00 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1801072003050.20912@carhart.net> (raw)
In-Reply-To: <20180007210715.eklhad@comcast.net>
Wow! That's excellent. It just digests fwcim and processes it like it is
supposed to. I wonder what's different. Are you setting your ua to
something other than edbrowse?
I had no idea we were doing so well on a major site.
On Sun, 7 Jan 2018, Karl Dahlke wrote:
> Well I'm rather baffled. I can sign in.
> I got rid of all the amazon cookies from my jar.
> Used ed to do this so there would be no collisions.
> Now I'm starting clean.
> I called up amazon.com, clicked on the sign in link, which takes me to the sign in page,
> entered login and password, click go, and there I am logged in.
> Actually it's Wendy's account, my wife, so you'll see the name Wendy.
> db3 log is at
> http://www.eklhad.net/amazon.wendy
> Yes I get the same uncallable js errors you get, and that is a concern, we have to figure that out,
> but it doesn't stop me from signing in.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2018-01-08 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 20:56 Chuck Hallenbeck
2018-01-08 1:18 ` Kevin Carhart
2018-01-08 2:07 ` Karl Dahlke
2018-01-08 4:16 ` Kevin Carhart [this message]
2018-01-08 7:55 ` Karl Dahlke
2018-01-08 7:57 ` Karl Dahlke
2018-01-08 12:07 ` Chuck Hallenbeck
2018-01-08 15:12 ` Karl Dahlke
2018-01-08 15:33 ` 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.1801072003050.20912@carhart.net \
--to=kevin@carhart.net \
--cc=baggett@Colorado.EDU \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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).