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] More edbrowse rejection
Date: Mon, 10 Feb 2014 17:05:35 -0800	[thread overview]
Message-ID: <87a9dye9wg.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140110195435.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 10 Feb 2014 19:54:35 -0500")

> I confirm, startpage doesn't work for edbrowse,
> This pisses me off!

I've seen other sites do it, too, but not in a while.  Some will give an
HTTP 403 response to a GET request from edbrowse.  Either kpfa.org or
kpfk.org was bad about this for a few months, but they seem to have
stopped that a long time ago.

Anyway, I think it's safe to assume that edbrowse is on some user-agent
shitlist out there.

-- Chris

      reply	other threads:[~2014-02-11  1:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  0:54 Karl Dahlke
2014-02-11  1:05 ` Chris Brannon [this message]

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=87a9dye9wg.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).