Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of nrstott@gmail.com designates
 209.85.216.173 as permitted sender)
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=kK1HJbfMvOcPHC9cnjjc/jGitOFdZYYUM2XOuC8QmwTVil/UvHd9JeUU6mpPyNrHft
         QPmBVyl53GL1fWAGrPtHrM7T41JQsFF01M+o9+lK99L+4Jnk7D1SOSlYPn9woGmBgFr8
         4CnYFYPbvVvIHeKZPzsb3b7kOO0q0UFIq+n1c=
MIME-Version: 1.0
In-Reply-To: <AANLkTinH23WWAiFPa3zb8qw7p6eucZVXvB+xcgQ9pW-Y@mail.gmail.com>
References: <AANLkTikOFnoKed-bXym02JNwq2iBGHtqspT6EwmO2urH@mail.gmail.com>
	<AANLkTi=O2oWvQVbh_y2Rm7wq3VGZcxguqW=cfPRv=BbU@mail.gmail.com>
	<AANLkTinRguFRj6gLaQ1ODtPFFGHzaW3Gwm2HH3s8+RCy@mail.gmail.com>
	<AANLkTinH23WWAiFPa3zb8qw7p6eucZVXvB+xcgQ9pW-Y@mail.gmail.com>
Date: Tue, 24 Aug 2010 08:32:33 -0500
Message-ID: <AANLkTinY3fN4yoSYfH6wh+yUEErU7eW+0fiOyKaGH2_y@mail.gmail.com>
Subject: Re: Bug in Password
From: Nathan Stott <nrstott@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It's saved in couch like "username@example.com"

I have saved users named "nrstott@gmail.com" for example and that's
how it shows up in the "name" field in the user doc

On Tue, Aug 24, 2010 at 4:43 AM, Benoit Chesneau <bchesneau@gmail.com> wrot=
e:
> On Tue, Aug 24, 2010 at 8:08 AM, Nathan Stott <nrstott@gmail.com> wrote:
>> You can reproduce it easily using curl or a web browser. =A0If your
>> username has an @ in it, you can't use URL authentication successfully
>> even if you url encode the username.
>>
>
> At the end couchdb see only the headers. So maybe it's the way the
> user was saved in the doc. Can you check how it is saved compared to
> the pparam you pass in your client or browser ?
>
> - beno=EEt