incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filipe David Manana <fdman...@gmail.com>
Subject Re: standalone attachments and content-encoding header
Date Tue, 23 Mar 2010 12:17:36 GMT
On Tue, Mar 23, 2010 at 9:02 AM, Benoit Chesneau <bchesneau@gmail.com>wrote:

> On Wed, Mar 17, 2010 at 11:53 PM, Filipe David Manana
> <fdmanana@gmail.com> wrote:
> > If the attachment request doesn't have "Accept-Encoding: deflate", then
> > couch needs to know the attachment is deflate compressed and uncompress
> the
> > attachment before sending it to the client. A missing Accept-Encoding
> header
> > is the same as "Accept-Encoding: identity, *;q=0".
> > Therefore you need to know the attachment was uploaded with deflate
> encoding
> > and how to uncompress it.
>
> I don't see why t should know. If couchdb don't know how to handle the
> attachment it should just send it with the content-type stored.
>
>
So, you would just send the attachment in deflate encoded form to the client
without letting him now that the attachment is deflated??


- benoit
>



-- 
Filipe David Manana,
fdmanana@gmail.com

"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message