From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.140.141.15 with SMTP id o15cs490292rvd; Tue, 19 Jan 2010 12:08:47 -0800 (PST) Received: from mr.google.com ([10.101.142.33]) by 10.101.142.33 with SMTP id u33mr9982891ann.43.1263931726652 (num_hops = 1); Tue, 19 Jan 2010 12:08:46 -0800 (PST) Received: by 10.101.142.33 with SMTP id u33mr587252ann.43.1263931724967; Tue, 19 Jan 2010 12:08:44 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.91.11.6 with SMTP id o6ls356954agi.3.p; Tue, 19 Jan 2010 12:08:42 -0800 (PST) Received: by 10.90.9.33 with SMTP id 33mr10172359agi.14.1263931722683; Tue, 19 Jan 2010 12:08:42 -0800 (PST) Received: by 10.90.9.33 with SMTP id 33mr10172356agi.14.1263931722587; Tue, 19 Jan 2010 12:08:42 -0800 (PST) Return-Path: Received: from mail-yx0-f151.google.com (mail-yx0-f151.google.com [209.85.210.151]) by gmr-mx.google.com with ESMTP id 18si657494ywh.13.2010.01.19.12.08.42; Tue, 19 Jan 2010 12:08:42 -0800 (PST) Received-SPF: pass (google.com: domain of james.a.rosen@gmail.com designates 209.85.210.151 as permitted sender) client-ip=209.85.210.151; Received: by mail-yx0-f151.google.com with SMTP id 15so10222160yxe.9 for ; Tue, 19 Jan 2010 12:08:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.101.165.32 with SMTP id s32mr591117ano.8.1263931722525; Tue, 19 Jan 2010 12:08:42 -0800 (PST) Date: Tue, 19 Jan 2010 12:08:42 -0800 (PST) In-Reply-To: <80d71444-3d71-4372-ae52-1169f20fef93@b10g2000yqa.googlegroups.com> X-IP: 129.83.31.1 References: <201001150005.30796.pirmin.kalberer@gmail.com> <80d71444-3d71-4372-ae52-1169f20fef93@b10g2000yqa.googlegroups.com> User-Agent: G2/1.0 X-HTTP-Via: 1.1 ironportb1.mitre.org:80 (IronPort-WSA/6.3.0-604) X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7,gzip(gfe),gzip(gfe) Message-ID: <1c395c10-551b-48a8-8fbd-4456bdf386d1@j19g2000yqk.googlegroups.com> Subject: Re: Rack::Access - Limit access based on IP address From: Gaius To: Rack Development X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of james.a.rosen@gmail.com designates 209.85.210.151 as permitted sender) smtp.mail=james.a.rosen@gmail.com X-Original-Sender: james.a.rosen@gmail.com Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: X-Thread-Url: http://groups.google.com/group/rack-devel/t/936968f4d92881ba X-Message-Url: http://groups.google.com/group/rack-devel/msg/9fa929f8a1d34259 Sender: rack-devel@googlegroups.com List-Unsubscribe: , List-Subscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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=A0pm, yonghui 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=A0am, Ryan Tomayko wrote: > > > On Thu, Jan 14, 2010 at 3:05 PM, Pirmin Kalberer > > > wrote: > > > Hi all, > > > For implementing a monitoring rack middleware I had to limit access t= o certain > > > URL's based on IP adresses. The attached patch for rack-contrib imple= ments > > > this. It borrows some ideas from rack-bug and code from Rack::URLMap.= .. > > > > -- Pull URL: > > > =A0git://github.com/pka/rack-contrib.git > > > Merged. > > > Thanks, > > Ryan > >