[
https://issues.apache.org/jira/browse/COUCHDB-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151328#comment-13151328
]
Adam Kocoloski commented on COUCHDB-1341:
-----------------------------------------
Hi Filipe, I wasn't proposing that the replicator use the AuthSession cookie in
making any subsequent requests. I agree that's asking for trouble. I just
wanted a `whoami` on the remote server instead of relying on the username in
the URL. It also seems like it would play more nicely with the advanced case
where the user adds an Authorization header to the replication request instead
of going for the proto://user:pass@host:port syntax.
> calculate replication id using only db name in remote case
> ----------------------------------------------------------
>
> Key: COUCHDB-1341
> URL: https://issues.apache.org/jira/browse/COUCHDB-1341
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Reporter: Bob Dionne
> Assignee: Bob Dionne
> Priority: Minor
>
> currently if the source or target in a replication spec contains user/pwd
> information it gets encoded in the id which can cause restarts if the
> password changes. Change it to use just the db name as the local case does,
> Here's a draft[1] of a solution.
> [1] https://github.com/bdionne/couchdb/compare/master...9767-fix-repl-id
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
