[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896905#action_12896905 ] Jochen Kempf commented on COUCHDB-720: -- Still struggeling I did another trial using fresh CouchDB installs on both server and client running Ubuntu 10.04. CouchDB versions are 0.11.1. I am using the nginx and iptables configuration listed here: https://gist.github.com/3b71763abdcd0f1ebd33 The couchdb log is also listed on the previous mentioned gist. As a few of you did manage to get replication working using ssl and nginx I must do something wrong. I would be so happy to get your help to finally figure out the problem and use CouchDB in a secure manner. Due to these problems I have to pass CouchDB credentials without ssl protection :-( 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885270#action_12885270
]
Klaus Trainer commented on COUCHDB-720:
---
Hi Couchers!
On my CouchDB 0.10.0 instance delivered with Ubuntu 10.04 amd64 I experience
the same pull replication problem (although I don't use a proxy or SSL etc.) in
the case I have an [admins] -entry (for instance admin = secret) in the
config file.
In my configuration, only the [httpd] port and the [admins] entry differ from
the original (i.e., default) CouchDB configuration.
The thing is that with that configuration all tests succeed, except the oauth
and the replication one.
For instance, when replicating, I get the following output:
kla...@devil:~$ curl -vX POST http://admin:sec...@127.0.0.1:5991/_replicate -d
'{source:test_suite_db_a,target:http://127.0.0.1:5991/test_suite_db_b}'
* About to connect() to 127.0.0.1 port 5991 (#0)
* Trying 127.0.0.1... connected
* Connected to 127.0.0.1 (127.0.0.1) port 5991 (#0)
* Server auth using Basic with user 'admin'
POST /_replicate HTTP/1.1
Authorization: Basic YWRtaW46c2VjcmV0
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
zlib/1.2.3.3 libidn/1.15
Host: 127.0.0.1:5991
Accept: */*
Content-Length: 77
Content-Type: application/x-www-form-urlencoded
HTTP/1.1 200 OK
Server: CouchDB/0.10.0 (Erlang OTP/R13B)
Date: Mon, 05 Jul 2010 16:15:13 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 378
Cache-Control: must-revalidate
{ok:true,session_id:280fe9ab1efeff12017da569ec443edf,source_last_seq:17,history:[{session_id:280fe9ab1efeff12017da569ec443edf,start_time:Mon,
05 Jul 2010 16:15:13 GMT,end_time:Mon, 05 Jul 2010 16:15:13
GMT,start_last_seq:0,end_last_seq:17,recorded_seq:17,missing_checked:0,missing_found:2,docs_read:2,docs_written:0,doc_write_failures:2}]}
(Just to clarify, it's basically the same output I see in Firebug when running
the Test Suite's replication test. Everything replicates fine, except _design
documents.)
When removing the [admins] entry from the config file, everything, including
replication of _design documents, works well:
kla...@devil:~$ curl -vX POST http://127.0.0.1:5991/_replicate -d
'{source:test_suite_db_a,target:http://127.0.0.1:5991/test_suite_db_b}'
* About to connect() to 127.0.0.1 port 5991 (#0)
* Trying 127.0.0.1... connected
* Connected to 127.0.0.1 (127.0.0.1) port 5991 (#0)
POST /_replicate HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
zlib/1.2.3.3 libidn/1.15
Host: 127.0.0.1:5991
Accept: */*
Content-Length: 77
Content-Type: application/x-www-form-urlencoded
HTTP/1.1 200 OK
Server: CouchDB/0.10.0 (Erlang OTP/R13B)
Date: Mon, 05 Jul 2010 16:19:37 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 378
Cache-Control: must-revalidate
{ok:true,session_id:220e214ea84bc5fe8c123e41db372fec,source_last_seq:17,history:[{session_id:220e214ea84bc5fe8c123e41db372fec,start_time:Mon,
05 Jul 2010 16:19:37 GMT,end_time:Mon, 05 Jul 2010 16:19:37
GMT,start_last_seq:0,end_last_seq:17,recorded_seq:17,missing_checked:0,missing_found:2,docs_read:2,docs_written:2,doc_write_failures:0}]}
I don't believe that this behavior is correct. Although my configuration is
different, I suppose it to be related to the present ticket.
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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885350#action_12885350 ] Filipe Manana commented on COUCHDB-720: --- Jochen, Your friendpaste URL pointing to your nginx config seems to be no longer available. I'm not experienced with nginx, but googling a bit, the following thread might help you: http://www.pubbs.net/200908/nginx/22292-proxycache-when-authorization-http-header-presents.html hope it helps 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885351#action_12885351
]
Filipe Manana commented on COUCHDB-720:
---
Klaus,
instead of
kla...@devil:~$ curl -vX POST http://admin:sec...@127.0.0.1:5991/_replicate -d
'{source:test_suite_db_a,target:http://127.0.0.1:5991/test_suite_db_b}'
try
kla...@devil:~$ curl -vX POST http://admin:sec...@127.0.0.1:5991/_replicate -d
'{source:test_suite_db_a,target:http://admin:sec...@127.0.0.1:5991/test_suite_db_b}'
(add user:passwd@ to the target url in the json content)
does it 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885352#action_12885352
]
Klaus Trainer commented on COUCHDB-720:
---
Filipe, thanks for the hint! Now that I've tried that it works
I know, you were actually hinting at that previously...
Curiously enough, I don't need to specify authentication neither in the request
URL, nor in the header, as long as I specify it in the JSON body:
kla...@devil:~$ curl -vX POST http://127.0.0.1:5991/_replicate -d
'{source:test_suite_db_a,target:http://admin:sec...@127.0.0.1:5991/test_suite_db_b}'
* About to connect() to 127.0.0.1 port 5991 (#0)
* Trying 127.0.0.1... connected
* Connected to 127.0.0.1 (127.0.0.1) port 5991 (#0)
POST /_replicate HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
zlib/1.2.3.3 libidn/1.15
Host: 127.0.0.1:5991
Accept: */*
Content-Length: 90
Content-Type: application/x-www-form-urlencoded
HTTP/1.1 200 OK
Server: CouchDB/0.10.0 (Erlang OTP/R13B)
Date: Mon, 05 Jul 2010 22:04:35 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 381
Cache-Control: must-revalidate
{ok:true,session_id:3716ed1b266f152ebce117accd073498,source_last_seq:19,history:[{session_id:3716ed1b266f152ebce117accd073498,start_time:Mon,
05 Jul 2010 22:04:35 GMT,end_time:Mon, 05 Jul 2010 22:04:35
GMT,start_last_seq:0,end_last_seq:19,recorded_seq:19,missing_checked:0,missing_found:17,docs_read:17,docs_written:17,doc_write_failures:0}]}
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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885356#action_12885356 ] Filipe Manana commented on COUCHDB-720: --- Klaus, great! :) 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885362#action_12885362 ] Jochen Kempf commented on COUCHDB-720: -- I'll take a look to the nginx proxycache discussion and see if that helps. @Klaus: I already commented the admin line out and additionally deactivated authentication setting the null authentication handler I took a look into the nginx log and here is the same 301 response that freezes replication: 201.215.36.77 - jochen [05/Jul/2010:18:44:18 -0400] GET /mytest/_local%2F4eddf88684f747f720130295073f965a HTTP/1.1 200 426 - CouchDB/0.11.0 201.215.36.77 - jochen [05/Jul/2010:18:44:19 -0400] GET /mytest/_changes?style=all_docsheartbeat=1since=4feed=normal HTTP/1.1 200 145 - CouchDB/0.11.0 201.215.36.77 - jochen [05/Jul/2010:18:44:20 -0400] GET /mytest/_design%2Ftest?open_revs=[\x221-967a00dff5e02add41819138abb3284d\x22]revs=truelatest=true HTTP/1.1 301 0 - CouchDB/0.11.0 Here is a link showing my nginx configuration: http://gist.github.com/464797 I still cannot successfully do pull replications! 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885379#action_12885379 ] Randall Leeds commented on COUCHDB-720: --- I believe the problem is that ibrowse does not specify basic auth headers automatically and couch_rep_httpc has to parse the url and add the appropriate options. I'm doing this work right now and will add info when I have it. 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885386#action_12885386 ] Randall Leeds commented on COUCHDB-720: --- I retract my previous statement. ibrowse is parsing the username/password. I had a feeling it must be, but I just didn't see it at first. Jochen: Is that nginx configuration shortened from a full version? I only see the _changes location. Where are the rules for other ssl connections? 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885037#action_12885037 ] Chris Anderson commented on COUCHDB-720: So it seems the 301 redirect following is the issue, not the authentication. We should verify that this is fixed in trunk before we cut 1.0 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12884795#action_12884795
]
Jochen Kempf commented on COUCHDB-720:
--
Daniel,
I tried your configuration with a complete new server setup and indeed I do not
get couchdb errors anymore when triggering a pull replication.
However, I still cannot do pull replication when the source db has design
documents in it.
Once it hits a design document a 301 http response is returned and the
replication process just freezes.
Here is a typical log entry:
[Fri, 02 Jul 2010 20:02:28 GMT] [info] [0.1132.0] 201.215.36.77 - - 'GET'
/rrhh_jobs/_design%2FJob?open_revs=[2854-eee80115b5b381b4f55a44b8cdd6dafb]revs=truelatest=true
301
I deactivated authentication in couchdb setting...
authentication_handlers = {couch_httpd_auth, null_authentication_handler}
What else can I do to make pull replication work?
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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879284#action_12879284 ] Daniel Truemper commented on COUCHDB-720: - Oh, sorry, kind of forgot about this ticket! At one point I decided to install nginx from source and finally got everything working with this configuration: http://www.friendpaste.com/2VzN9vD63KV6JDUWQdIT1X Strangely I was not able to reproduce the error! So now, everything works as I'd expected it! Best Daniel 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866548#action_12866548
]
Jochen Kempf commented on COUCHDB-720:
--
Daniel,
this is the error I get on the client when using a free test ssl cert (only
appears when doing the pull replication):
[Wed, 12 May 2010 11:51:32 GMT] [error] [0.20.0] {error_report,0.8.0,
{0.20.0,std_error,
File operation error: eacces. Target: ./ssl_alert.beam.
Function: get_file. Process: code_server.}}
[Wed, 12 May 2010 11:51:33 GMT] [error] [0.30930.100] SSL:
certify_certificate: ./ssl_handshake.erl:486:Fatal error: handshake_failure
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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12865731#action_12865731 ] Daniel Truemper commented on COUCHDB-720: - @Filipe: no, exactly the same behaviour. @Jochen: yes, the number of replicated documents vary. Seems like the way you described it: once the _design doc is reached, pull replication stops. Regarding the SSL cert: I am using a CA that I created for this with a server cert signed by that CA. Where do you get the invalid ssl error? CouchDB Server/Client? 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864698#action_12864698 ] Daniel Truemper commented on COUCHDB-720: - Hi, I just experienced the same behaviour but have some more background information. I have an nginx reverse proxy for the ssl stuff. On both DBs there are users and admins. From the client DB I am now trying to do the following in Futon: - start replication from https://$user:pas...@$server:5984/$db to http://localhost:5984/$db (on the local machine I am already logged in and on both DBs I am admin). When I try to replicate using pull replication, all documents are replicated except the design document. At the time the replicator tries to GET the design document a HTTP 401 is being sent from the server DB. When I do the same using push replication the design document is being replicated. I am unsure if this is intentional but if so I could use a little help ;). Best Daniel 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.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864730#action_12864730 ] Filipe Manana commented on COUCHDB-720: --- Daniel, if you: - specify source as https://$user:pas...@$server:5984/$db - and target as http://$user:pas...@$localhost:5984/$db does it work? 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.
