Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 62375 invoked from network); 17 Feb 2009 22:46:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Feb 2009 22:46:36 -0000 Received: (qmail 16397 invoked by uid 500); 17 Feb 2009 22:46:30 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 16355 invoked by uid 500); 17 Feb 2009 22:46:29 -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 16344 invoked by uid 99); 17 Feb 2009 22:46:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 14:46:29 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.132.244 as permitted sender) Received: from [209.85.132.244] (HELO an-out-0708.google.com) (209.85.132.244) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 22:46:22 +0000 Received: by an-out-0708.google.com with SMTP id c37so1120878anc.5 for ; Tue, 17 Feb 2009 14:46:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=E5PXlcv4aDO76KRwgg50+ODCG4yR0SXwKBIyHQe6Xs8=; b=SDx3HMPjqbXODd8g1iKxWFzuQtpMXlzBbgyIGOBQfmefzM4MEbfqx1MpQSrrul7PVH eje1uusecxr9GGyXOyCTnHADWlE6KNItd3pNo/wyiK/t0C6uAAlsGXgOAf9v6m/T4YUi /iXS8EiJ0TEfNxYIjXLN3KhunyBtTHTHTx9qc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=xt9/z6raf7h3xPcxmMvqIApSOtWTc/qyUXIPZj5x6ye66N3JkTTeM5fQHXnDK2Gzyu V0LP77e+EH0+gM22ySaa8cXibskLCUO9WFev5kEAsUxNKu08k6moCXoGTbYUySvmIysY 4wRFhtjqDrq0bcGsW0Op8IFWtTmUIhCcNnTk4= MIME-Version: 1.0 Received: by 10.231.13.136 with SMTP id c8mr1311572iba.45.1234910760870; Tue, 17 Feb 2009 14:46:00 -0800 (PST) In-Reply-To: <41b0fe890902171438lec7642cwf6371b8b1a7f6c8e@mail.gmail.com> References: <41b0fe890902162338m20f12659yb0ac134d71cbc60@mail.gmail.com> <41b0fe890902171438lec7642cwf6371b8b1a7f6c8e@mail.gmail.com> Date: Tue, 17 Feb 2009 17:46:00 -0500 Message-ID: Subject: Re: http header options From: Paul Davis To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org There are very few headers specific to CouchDB. Grepping X-CouchDB in the source should reveal them. I know of no wiki page yet on this topic. Though contributions are welcome. As to the standard HTTP headers, you'll want to look also at what MochiWeb supports. Pretty sure its fully HTTP/1.1 compliant so whatever that entails. I know that Keep-Alive and piplining are supported. Oh, also quite a few urls produce Etags headers, so if your client also understands those you can do caching stuff. HTH, Paul Davis On Tue, Feb 17, 2009 at 5:38 PM, Rhett Garber wrote: > Bump.... > really ? Nothing ? > > On Mon, Feb 16, 2009 at 11:38 PM, Rhett Garber wrote: >> Is there a document somewhere that describes all the available http >> header's that couchdb will understand ? >> >> I've heard references to forcing an fsync. I'm also curious about >> Keep-Alive. Haven't been able to find anything on the wiki. >> >> Thanks, >> >> Rhett >> >