edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] A possible login issue on gkg.net
Date: Tue, 6 Mar 2018 15:54:38 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1803061547210.20263@carhart.net> (raw)
In-Reply-To: <20180206184230.eklhad@comcast.net>



Just regarding the cookies message, I find that this sometimes displays 
even though it isn't true.  There's a lot of these situations where mutually 
exclusive statements are both in the HTML, and one is intended to be 
removed by JS.  It could say "You are logged in," "You are logged out."

I think the login screen of amazon says "you must enable 
cookies" at the top, but we certainly did have cookies working all 
throughout the recent amazon adventure.  Beware believing all assertions 
that are sitting in html.  Sorry this isn't specific help on gkg - I will 
try to pull this up specifically in a little while.



On Tue, 6 Mar 2018, Karl Dahlke wrote:

> Did you look at the page, despite the 403 error?
> There's another login form, and it also says we need to activate cookies,
> which suggests perhaps a problem with edbrowse and cookies,
> and it also says you have to pass a captcha to log in, which suggests you are out of luck.
> IDK
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>

---

  reply	other threads:[~2018-03-06 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 23:31 Chuck Hallenbeck
2018-03-06 23:42 ` Karl Dahlke
2018-03-06 23:54   ` Kevin Carhart [this message]
2018-03-07 12:30     ` Karl Dahlke

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.1803061547210.20263@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).