edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] startpage
Date: Mon, 10 Feb 2014 15:52:17 -0800	[thread overview]
Message-ID: <87iosmedam.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140110144757.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 10 Feb 2014 14:47:57 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> There is something else amiss about the way we submit that query.

I get the same thing, even when JavaScript is disabled.
My guess is that they're expecting some form field that we're not
sending.  It's supposed to be filled in by JavaScript, and if we don't
send it, they assume that we're using some kind of automation to access
their site.  Automation usually isn't "smart" enough to run JavaScript.
And our JS implementation is hitting a snag somewhere, failing to fill
in that field.
I'd try this in Chromium with ChromeVox, but I have no way to see what
query the browser is sending to the server.  If this were a plain http
connection, I'd dump the traffic to a file with tcpdump and extract what
I need.  But it's https.  I'm looking into mitmproxy, which may help me
to examine the traffic.

-- Chris

  parent reply	other threads:[~2014-02-10 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 19:47 Karl Dahlke
2014-02-10 20:40 ` Chuck Hallenbeck
2014-02-10 23:52 ` Chris Brannon [this message]
2014-02-11  0:04   ` Chuck Hallenbeck
2014-02-11  0:29     ` Chris Brannon
2014-02-11  0:42       ` Chuck Hallenbeck
  -- strict thread matches above, loose matches on Subject: below --
2014-02-09 23:23 Karl Dahlke
2014-02-09 19:04 Karl Dahlke
2014-02-09 22:12 ` Chris Brannon
2014-02-09 17:35 Karl Dahlke
2014-02-09 18:29 ` Chris Brannon

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=87iosmedam.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --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).