Hopefully I can figure out one day what is going wrong with ssl
replication (nginx) - by now I just exclude design docs from
replication using a replication filter.
Filter doc:
{
"_id": "_design/Replication",
"_rev": "1-26c7c5e5b28a0b67caad16540207982e",
"filters": {
"no_design": "
Has anyone else tried pull replication with ssl secured CouchDB 0.11.2?
I just tried it and.still the same problem: design_docs are not
replicated :(
Here is the log:
[Fri, 13 Aug 2010 01:03:26 GMT] [info] [<0.31773.0>] 201.215.27.127 -
- 'GET'
/test/_design%2FTest?open_revs=["3-fd3452225ed1
Hi Daniel,
I also tried replication disabling basic auth and setting the
authorization header with "proxy_set_header Authorization
$http_authorization;" in nginx.
Unless I didn't do something wrong here it should work, right?
But I get the same error during replication!
I think I'll have to wait
Hi,
From the gist I see that you have enabled basic authentication inside nginx.
Why so? Try do disable it and only use the CouchDB authentication.
In the "http response of replication" the 401 is from nginx not CouchDB. So
maybe it gets mixed up somewhere...
Daniel
> Hi,
>
> I have been try
Hi,
I have been trying to figure out quite for a while why I cannot do
"pull replication using nginx basic authentication on the source
system.
I simply do not know what I am doing wrong nor why couchdb fails
replicating giving a not authorized error considering I can
successfully do a put request
