Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <4872453.510761282580417758.JavaMail.jira@thor>
Date: Mon, 23 Aug 2010 12:20:17 -0400 (EDT)
From: "Adam Kocoloski (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-868) Authenticated replication fails for
 docs with long revision histories
In-Reply-To: <3887842.510491282578977123.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901464#action_12901464 ] 

Adam Kocoloski commented on COUCHDB-868:
----------------------------------------

I'm a little confused.  The ticket refers to docs with long revision histories, but the patch deals with attachments.  Does this patch actually fix a bug with long revision histories, or just one regarding attatchments that nrstott was bumping into on IRC?

> Authenticated replication fails for docs with long revision histories
> ---------------------------------------------------------------------
>
>                 Key: COUCHDB-868
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-868
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.0, 1.0.1
>         Environment: Linux, Erlang R13B04
>            Reporter: Jason Smith
>            Assignee: Filipe Manana
>         Attachments: 0001-Correctly-redirect-during-authenticated-replication.patch
>
>
> The old bug of forgetting the Authorization header still happens, apparently with documents attachments. I think the request for _design%2fddoc/attachment is bounced and the subsequent request simply follows the `Location` header without adding the credentials again.
> It looks like couch_rep_att:validate_headers/3 simply follows the "Location" header instead of doing what couch_rep_httpc's smarter `redirect_url/2`

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.