From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] startpage
Date: Mon, 10 Feb 2014 14:47:57 -0500 [thread overview]
Message-ID: <20140110144757.eklhad@comcast.net> (raw)
You aren't being blocked per se; I get the same message,
and I don't believe in coincidences.
There is something else amiss about the way we submit that query.
Probably should run it with db4,
especially noting the redirection to smartpage,
and compare that with what happens in another browser.
Karl Dahlke
next reply other threads:[~2014-02-10 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 19:47 Karl Dahlke [this message]
2014-02-10 20:40 ` Chuck Hallenbeck
2014-02-10 23:52 ` Chris Brannon
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=20140110144757.eklhad@comcast.net \
--to=eklhad@comcast.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).