couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kempf (JIRA)" <>
Subject [jira] Commented: (COUCHDB-720) Pull replication fails due to "401 Authentication required" while push replication works fine
Date Sat, 08 May 2010 13:45:48 GMT


Jochen Kempf commented on COUCHDB-720:

Hi Daniel,

could you try to delete the db on the client and retry replication to check whether all docs
(except the _design ones) are replicated? For me, the number of replicated docs is varying
 - if the db is pretty big and no previous replication took place just a part of the normal
docs get replicated.

It seems that once the _design doc is being accessed the whole replication process stops and
depending on how many docs were replicated before the final number of replicated docs changes.

Another question is what type of ssl cert you are using. I tried both a self signed cert and
a free cert from startssl (I still couldn't try a commercial one as I cannot get a trial version
that is completely trusted).

hen using a self signed cert no specific logs are written, just the 401 error for pull replication.
When using a free cert from startssl I get an "invalid ssl" error log.

> Pull replication fails due to "401 Authentication required" while push replication works
> ---------------------------------------------------------------------------------------------
>                 Key: COUCHDB-720
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Futon, HTTP Interface, Replication
>    Affects Versions: 0.10.1, 0.11
>         Environment: Remote server having Nginx reverse proxy and basic authentication
>            Reporter: Jochen Kempf
>            Priority: Blocker
> Pull replication fails using both Futon Replicator and http request throwing an "401
Authentication required" error. This just happens when design documents are existent.
> Push replication on the other hand works fine.
> See used code here:

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

View raw message