From: Gaius <james.a.rosen@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Rack::Access - Limit access based on IP address
Date: Tue, 19 Jan 2010 12:08:42 -0800 (PST) [thread overview]
Message-ID: <1c395c10-551b-48a8-8fbd-4456bdf386d1@j19g2000yqk.googlegroups.com> (raw)
In-Reply-To: <80d71444-3d71-4372-ae52-1169f20fef93@b10g2000yqa.googlegroups.com>
As implemented, it seems Rack::HostWhiteList or
Rack::Auth::HostWhiteList might be a good name. It would be possible
to modify the code to support both white- and black-lists. In that
case, Rack::Auth::HostAccess might work.
On Jan 19, 1:58 pm, yonghui <yonghui....@gmail.com> wrote:
> Apache 2.2 renamed mod_access to mod_authz_host. Do we need a more
> descriptive name for this middleware?
>
> On Jan 15, 7:34 am, Ryan Tomayko <r...@tomayko.com> wrote:
>
> > On Thu, Jan 14, 2010 at 3:05 PM, Pirmin Kalberer
>
> > <pirmin.kalbe...@gmail.com> wrote:
> > > Hi all,
> > > For implementing a monitoring rack middleware I had to limit access to certain
> > > URL's based on IP adresses. The attached patch for rack-contrib implements
> > > this. It borrows some ideas from rack-bug and code from Rack::URLMap...
>
> > > -- Pull URL:
> > > git://github.com/pka/rack-contrib.git
>
> > Merged.
>
> > Thanks,
> > Ryan
>
>
prev parent reply other threads:[~2010-01-19 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 23:05 [Patch] Rack::Access - Limit access based on IP address Pirmin Kalberer
2010-01-15 12:34 ` Ryan Tomayko
2010-01-19 18:58 ` yonghui
2010-01-19 20:08 ` Gaius [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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c395c10-551b-48a8-8fbd-4456bdf386d1@j19g2000yqk.googlegroups.com \
--to=rack-devel@googlegroups.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 read-only IMAP folder(s) and NNTP newsgroup(s).