Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 8417 invoked from network); 1 Apr 2010 02:27:07 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 02:27:07 -0000 Received: (qmail 82631 invoked by uid 500); 1 Apr 2010 02:27:06 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 82603 invoked by uid 500); 1 Apr 2010 02:27:06 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 82595 invoked by uid 99); 1 Apr 2010 02:27:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 02:27:06 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 74.125.83.52 as permitted sender) Received: from [74.125.83.52] (HELO mail-gw0-f52.google.com) (74.125.83.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 02:26:57 +0000 Received: by gwb17 with SMTP id 17so517982gwb.11 for ; Wed, 31 Mar 2010 19:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=KpmOfACDT9uMtcAc8queA5GVHtGi11LjVyj9c0y5lkM=; b=rGm/lZHRdROD851/Jwwq4RP6XZgYbKZ8KF8q/NvGg7D3YtJcOUWzU+Gu6mdPShU6Mb ya2zt19xBzfrIw4JGvbpjdrrla6MK6G3gX03+47ivy4YcHL5R/wH4E4Zhj/lFJpHbZu3 AA1/naRcQBCp30OfJKWbM2XQw55Aek44ZS5iI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=v16NH3TyGoHU5uX4bw27o4fREcz+xKrh5sPEnwT7/0lX5hMjgtQIUx+U+Tx2sIzOXd uDparBUvawx1TstSdsgN35Smo+yhpNow/6qwAHEBeJfMpyOdrvyTe9kRP8qVDSiUhDHW f3aktq3mo5VOMBx/XmHg+s0ayWbdgrMYwWbos= Received: by 10.150.160.8 with SMTP id i8mr784466ybe.141.1270088796077; Wed, 31 Mar 2010 19:26:36 -0700 (PDT) Received: from [192.168.1.103] (c-98-248-172-14.hsd1.ca.comcast.net [98.248.172.14]) by mx.google.com with ESMTPS id cm22sm7622255ibb.5.2010.03.31.19.26.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 19:26:35 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: Require login to see any data in a CouchApp? From: J Chris Anderson In-Reply-To: Date: Wed, 31 Mar 2010 19:26:33 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5CBFE1E3-27B6-47F7-99E0-1AC0A49D433B@gmail.com> References: To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1077) X-Virus-Checked: Checked by ClamAV on apache.org On Mar 31, 2010, at 6:01 PM, David Goodlad wrote: > On Thu, Apr 1, 2010 at 11:56 AM, Zachary Zolton > wrote: >> That's fair, I'll make a separate login DB+app. >>=20 >> Is there some way I can replace that "unauthorized error" JSON >> response with a redirect to my login page? Given that the auth cookie >> times out, I'll need to send users back to login screen = occassionally. >>=20 >> If not, perhaps this would be a useful feature. >=20 > Agreed, I've run into this as well. >=20 I'd be happy to see this. Shouldn't be hard to write. It's probably = worth discussing the implementation plan on the dev list to make sure = it's a simple as possible.=20 Chris