Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 14753 invoked from network); 22 Jun 2010 13:22:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Jun 2010 13:22:15 -0000 Received: (qmail 44032 invoked by uid 500); 22 Jun 2010 13:22:14 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 43660 invoked by uid 500); 22 Jun 2010 13:22:11 -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 43652 invoked by uid 99); 22 Jun 2010 13:22:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jun 2010 13:22:10 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of truemped@googlemail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jun 2010 13:22:04 +0000 Received: by bwz16 with SMTP id 16so3035217bwz.11 for ; Tue, 22 Jun 2010 06:21:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.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=tt2Uu8rk8aff28+ScmQ63c8khsbF5Krl3Clbji4O+r0=; b=JyiyiK4D2A/wqxBmd1ddWAiywF11oGV0+7ugo3P5Ml5FalADhdKA1Ou4AzzFgd3rG8 lOfoWz+jGSf5M6FCboaz0LjoO3wlmflB246v+hH/tP1dOs6rOPi3ZwXHXeUqgVbXfOIQ ScGur6H9CdQNwk0Vk7LH3fLzrupCGj8GBx8fQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=IMJ3BmhmICL7kNZqUAvPlKD/0qnu/aM5y2ma/VVbGxZ+EYSM2xN3c9h2Kf0ZHNh3kG tyB2hE3DvJrO87IlCXwmVebcFHgvywWrOo1SiTQOitBTECCcqKj8P4vewJZYbx2QbraK 05/xmviR2OPsIIdO9VedFbY6Qt5qYvZ70lXaw= Received: by 10.204.79.214 with SMTP id q22mr2707311bkk.109.1277212902372; Tue, 22 Jun 2010 06:21:42 -0700 (PDT) Received: from vandusen.neofonie.priv (crt-01-tr.neofonie.de [91.213.91.28]) by mx.google.com with ESMTPS id jr10sm10102778bkb.42.2010.06.22.06.21.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 06:21:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1081) Subject: Re: hidden fields in a document From: Daniel Truemper In-Reply-To: Date: Tue, 22 Jun 2010 15:21:38 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <6FE178C8-822E-4FAD-ABAA-F47E4248FEC7@googlemail.com> References: To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1081) Hi, > I have a need where certain fields in a document shouldn't seen while > responding for GET document API's. For e.g the document store's = certain > fields which are internal to the application not to be seen by end = user. Why do you store the data along the document the end-user will see? You = could easily create another document with your app specific data and = create a reference to the original document. With a view you could GET = them both at the same time. In order to "protect" specific documents from the outside world you = should use a reverse proxy (something like nginx) and forbid access to = certain URLs. Best Daniel=