[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885235#action_12885235
]
Jochen Kempf commented on COUCHDB-720:
--------------------------------------
Here are the details of my system configuration in order to help you reproduce
the issue:
- Remote Machine: Ubuntu 10.04 Server, Nginx Webserver with SSL (self signed
certificate and applying this configuration:
http://www.friendpaste.com/2VzN9vD63KV6JDUWQdIT1X), CouchDB 0.11, CouchDB
Lucene -0.6.0, CouchDB Authentication is disabled by setting the null
authentication handler
- Local Machine: Ubuntu 9.10, CouchDB 0.11
Databases to be replicated must have at least one design document to trigger
the issue. I would recommend to trigger a pull replication on the local machine
with the remote DB having the design document and the local machine not. Then
the replication process should freeze once the desing document on the remote
machine is hit.
I used the full url syntax for replication (both in Futon and console):
{"target": "http://user:passw...@localhost:5984/db";, "source":
"http://user:passw...@remote/db"} - thus the remote machine directly redirects
to the 5984 port without need to specify it.
I hope you can reproduce and fix that issue before the 1.0 release as I really
cannot use CouchDB in my application due to that issue.
Thanks for your help!
> Pull replication fails due to "401 Authentication required" while push
> replication works fine
> ---------------------------------------------------------------------------------------------
>
> Key: COUCHDB-720
> URL: https://issues.apache.org/jira/browse/COUCHDB-720
> 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 enabled
> 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: http://gist.github.com/364072
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
