Nathan, This ticket: https://issues.apache.org/jira/browse/COUCHDB-868
Fixes the issue, as pointed by Adam. I just added a test case for this specific use case to 1.0.x branch and trunk: http://svn.apache.org/viewvc?view=revision&revision=1034376 The test fails on 1.0.1 (and bellow), as expected, but succeeds in 1.0.x and trunk. regards, On Sun, Sep 19, 2010 at 2:01 PM, Jan Lehnardt <[email protected]> wrote: > > On 24 Aug 2010, at 18:26, Nathan Stott wrote: > >> I tried it, didn't fix my issue. > > Can you open a new JIRA issue for this so we won't forget about it? > > Cheers > Jan > -- > > >> >> On Tue, Aug 24, 2010 at 9:38 AM, Adam Kocoloski <[email protected]> wrote: >>> Hi Nathan, did you get a chance to see if >>> https://issues.apache.org/jira/browse/COUCHDB-868 fixed this issue? >>> >>> Adam >>> >>> On Aug 23, 2010, at 3:57 PM, Nathan Stott wrote: >>> >>>> I've identified a bug in replication in couchdb. >>>> >>>> Here are the steps to reproduce: >>>> >>>> Create a user named "bubba" >>>> Create a database with a design document that has attachments. >>>> Make this database have "bubba" as an admin and set a reader role of >>>> "readme" >>>> >>>> Try to replicate this DB on another machine with credentials for bubba >>>> in the URL (http://bubba:passw...@remotemachine:port/mydb) >>>> >>>> You will receive 401s in the log in attachments. It does not matter >>>> whether you give bubba the "readme" role or not, the results are the >>>> same. Remove the attachment and the design doc will replicate fine. >>>> Remove the "readers" from the security object of the DB and the desing >>>> doc will replicate fine. >>>> >>>> This is tested and reproduced on 1.0.1 >>> >>> > > -- Filipe David Manana, [email protected], [email protected] "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men."
