Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Disabling doc include
From: Robert Newson <rnewson@apache.org>
In-Reply-To: <ACE57B78-1CE5-4D4F-AAB5-032415799F52@couchbase.com>
Date: Wed, 1 Jan 2014 23:27:41 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C582CB4-CAA4-4BB4-A4EB-9529E177F0C9@apache.org>
References: <52C28C30.7010809@meredrica.org>
 <CAHdjipKDnJL=FMsB9LFzLR2oLTLV6n-+5rc_G06+XX_Y1J-m1w@mail.gmail.com>
 <52C291F9.80708@meredrica.org>
 <ACE57B78-1CE5-4D4F-AAB5-032415799F52@couchbase.com>
To: user <user@couchdb.apache.org>

"there=92s no notion of read-protection in CouchDB."

There=92s no document level read protection, but you can certainly grant =
or deny read access to users on a per database basis. That=92s by design =
due to the ease that information could leak out through views =
(particularly reduce views). The restrictive proxy approach is brittle, =
it requires that you know all the URL patterns to block and keep them up =
to date when you upgrade CouchDB. It can work, it=92s just not awesome.

B.

 .

On 1 Jan 2014, at 20:47, Jens Alfke <jens@couchbase.com> wrote:

>=20
> On Dec 31, 2013, at 1:44 AM, meredrica <stuff@meredrica.org> wrote:
>=20
>> I expose CouchDB directly to mobile clients and wanted to hide some=20=

>> information from them.
>=20
> You can=92t really do that; there=92s no notion of read-protection in =
CouchDB.
> As a workaround you can put CouchDB behind a proxy or gateway, and =
restrict the URL patterns that clients are allowed to send.
>=20
> =97Jens
>=20