Karl Dahlke <[email protected]> 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 _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
