Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of b.candler@pobox.com
 designates 208.72.237.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to
	:subject:message-id:references:mime-version:content-type
	:in-reply-to; q=dns; s=sasl; b=nOb+lKZNns9fnnO5s4LfWJTD+hJGOEafi
	cMGaO8sbX8JVkB0n1VGH+jTmB9ZVK02cWuBToQT3/4JKGW5qsHJP3ikegUG6hLgD
	oXo7Sx+izxjOwWIMM14NUK8xDj+2lsBREVuoRMWvIGPU6XHIWzR2IgnCQDaOwHAo
	TOXaqAVhnw=
Date: Wed, 17 Mar 2010 20:24:33 +0000
From: Brian Candler <B.Candler@pobox.com>
To: user@couchdb.apache.org
Subject: Re: standalone attachments and content-encoding header
Message-ID: <20100317202433.GB15544@uk.tiscali.com>
References: <70763547-33D8-475C-90FC-296E3D46B4E3@merrells.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <70763547-33D8-475C-90FC-296E3D46B4E3@merrells.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, Mar 17, 2010 at 12:39:15PM -0700, John Merrells wrote:
> I just started working with couch and I have a question about the headers
> returned with a standalone attachment.  I'm storing compressed html files
> as an attachment, sending the headers content-type: text/html and
> content-encoding: deflate.  When the attachment is fetched the correct
> content-type is returned, but no content-encoding header is returned.  Is
> this a limitation of CouchDB?  Or, perhaps of my client (CouchRest)?  Or,
> perhaps I've just made a mistake.

Try adding --compressed option to curl command line (and GET not HEAD).
This should add "Accept-Encoding: deflate, gzip" header to the request. That
is - if the client doesn't ask for a compressed representation, I don't
think couchdb will send it.