[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.
Re: _changes timeout has a max of 60 seconds?
On 7 May 2010, at 20:30, Sebastian Cohnen wrote: I took the liberty to add this information to the wiki :) 100 Internets for you, my good sir :) Cheers Jan -- On 07.05.2010, at 18:51, Damien Katz wrote: This is the intent. The max timeout value is set in the ini. The reason we do this is to prevent lots of undetected dead connections using up resources, which can happen if the TCP connection dies abnormally. To get around the timeout, you up the changes_timeout in the ini: [httpd] changes_timeout=#millisecs Or you have the server send a heartbeat. Then the connection can stay open indefinitely, and the heartbeats cause dead connections to be detected by the server. -Damien On May 6, 2010, at 10:24 PM, Mark Hammond wrote: I'm trying to use _changes with feed=continuous and a timeout greater than the default - however, couch always uses the default of 60 seconds. Timeouts smaller than the default work as expected. It seems get_changes_timeout/2 in couch_changes.erl is responsible for this by selecting the smallest of the specified and default timeout. While is sounds reasonable to have a default of 60 seconds, there doesn't seem to be an obvious case for also making that the max - *some* maximum might be reasonable, but 60 seconds seems pretty low. Should I open a bug, or is this really the intent? If the latter, I'll update the wiki accordingly... Thanks, Mark
