Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jens@couchbase.com designates
 199.193.200.197 as permitted sender)
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: authentication issues
From: Jens Alfke <jens@couchbase.com>
In-Reply-To: 
 <CAB8ffCC9HK1c8m1YyD+WuEsj7eRGRh_geV31pda=hBu9jTwBKw@mail.gmail.com>
Date: Thu, 15 May 2014 17:02:52 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <E160B5B1-15BC-4224-A4C9-809F683FAAFA@couchbase.com>
References: 
 <CAB8ffCC9HK1c8m1YyD+WuEsj7eRGRh_geV31pda=hBu9jTwBKw@mail.gmail.com>
To: <user@couchdb.apache.org>


On May 14, 2014, at 7:36 AM, Will Holcomb <will@dhappy.org> wrote:

> I have a couch server running and I am attempting to access it from a =
web
> application server from port 80. I am having difficulty =
authenticating.

CouchDB doesn=92t send a WWW-Authenticate header in the response when it =
returns a 401 status. There was some reason for doing this (having to do =
with clients accessing CouchDB from a web browser?) but it=92s =
nonstandard and it really messes up a lot of HTTP client libraries.

The workaround is to edit your CouchDB config and add a new variable to =
the =91httpd=92 section, whose key is =93WWW-Authenticate=94 and value =
is something like
	Basic realm=3D=93CouchDB"

And it gets worse! You have to do this workaround *every time CouchDB =
starts up* because it fails to persist the changed config properly =97 =
after relaunch the key will have changed to =93www-authenticate=94 which =
doesn=92t work.

Yes, I filed a bug on this. It=92s really annoying.

=97Jens=