Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.198.247 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Bl5Hxhk8xYZpUo2IRRDwwRkkxaJSimiJc2RcaWbxTTghyNUZ0fSQijNPhClyDVgW6QRWXVlfQWT/OaUR2lQHW56RL2Po9wuR1B3/ySm+KhZHa7JSeMC2GneE/ZcQ8c1mmbvfjXrEfxgCLlHwGCVaesyLxyt596q1JEZ64NfT2JI=
Message-ID: <b7cd8ed10804231127q76d55f43j87335fa8c4944243@mail.gmail.com>
Date: Wed, 23 Apr 2008 20:27:28 +0200
From: "Benoit Chesneau" <bchesneau@gmail.com>
To: couchdb-user@incubator.apache.org
Subject: Re: Erroneous output from the trunk?
In-Reply-To: <6F3CD0A6-77CF-4451-9E49-87A51F432EB0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <B04198C509E7ED47A0E3191B132CC48A012A4058@melbmail.pronto.com.au>
	 <2A67D687-745D-4FDB-9ECE-2491EB48A817@gmail.com>
	 <C1066EF5-E765-43AC-B05B-E0F9D8A304A1@bluebridge.jp>
	 <241FC5B1-8820-4492-B73D-5500465C90FD@gmail.com>
	 <b7cd8ed10804230908t48f4eed4y40ef2646fcbce4a1@mail.gmail.com>
	 <2CB74745-B717-4931-8F35-843D13F8805E@gmail.com>
	 <b7cd8ed10804231015p9b41739vbeaf687287667e6b@mail.gmail.com>
	 <6F3CD0A6-77CF-4451-9E49-87A51F432EB0@gmail.com>

On Wed, Apr 23, 2008 at 8:22 PM, Guby <guby.mail@gmail.com> wrote:
> I access it through nginx, but this worked perfectly until I updated
> couchdb. The nginx config looks like this:
>
>  upstream db {
>         server 127.0.0.1:5984;
>  }
>
>  server {
>         listen 80;
>         server_name my_domain.com;
>         location / {
>                 proxy_pass http://db;
>                 auth_basic "Restricted area";
>                 auth_basic_user_file /path_to_password_file/.htpasswd;
>                 break;
>         }
>  }
>
>  Here are the headers from Firefox:
>
>  Response Headers
>  Transfer-Encoding       chunked
>  Date    Wed, 23 Apr 2008 16:00:36 GMT
>  Content-Type    text/plain;charset=3Dutf-8
>  Server  nginx/0.5.26
>  Content-Encoding        gzip
>
>  Request Headers
>  Host    db.kle.io
>  User-Agent      Mozilla/5.0 (Macintosh; U; Intel Mac OS X; nb-NO;
> rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
>  Accept
> text/xml,application/xml,application/xhtml+xml,text/html;q=3D0.9,text/pla=
in;q=3D0.8,image/png,*/*;q=3D0.5
>  Accept-Language nb,no;q=3D0.8,nn;q=3D0.6,en-us;q=3D0.4,en;q=3D0.2
>  Accept-Encoding gzip,deflate
>  Accept-Charset  ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7
>  Keep-Alive      300
>  Connection      keep-alive
>  Authorization   Basic c2ViYXN0aWFuOnNlYmJhODU=3D
>
>
>  Best regards
>  Sebastian
>


ok. So this is a known problem, nginx converse with couchdb in http
1.0 like most of proxies. So you get a non parsed http chunks.

I made a patch for that (though non tested with latest trunk) :
You can get it here :
https://issues.apache.org/jira/browse/COUCHDB-40

don't hesitate to comment this issue :)

Beno=EEt


--=20
- beno=EEt