The easiest way is indeed to put CouchDB behind a proxy, but for
_all_docs you can just remove this http endpoint from config by adding
the following in your local.ini
[httpd_db_handlers]
_all_docs =
Suddenly, for _purge you cannot do the same trick. However, you might
want to open issue on JIRA
To retrieve document of specific revision, you need to perform a
request against document resource with ?rev= query parameter contained
specific revision value
/db/docid?rev=1-abc
To retrieve all conflicts, use ?open_revs=all one:
/db/docid?open_revs=all
See also:
On 30 Dec 2014, at 09:01 , Alexander Shorin kxe...@gmail.com wrote:
The easiest way is indeed to put CouchDB behind a proxy, but for
_all_docs you can just remove this http endpoint from config by adding
the following in your local.ini
[httpd_db_handlers]
_all_docs =
Suddenly, for
On 29 Dec 2014, at 21:04 , Stephan Wissel step...@wissel.net wrote:
Hi there,
I have a timeout problem with my replications. My replication request
roughly looks like:
(I started with https, but now test with http first, step by step)
{
target: wisselblog,
source: {
Hi Cory, line 440 in the 1.2.1 release of Apache CouchDB looks like this:
{ok, RawBin:TotalBytes/binary} = file:pread(Fd, Pos, TotalBytes),
Your initial mail reported a 'badmatch' error on this line and indicated a
response of the form {ok, Bin}. The match that's failing is therefore the
The easiest way is indeed to put CouchDB behind a proxy, but for
_all_docs you can just remove this http endpoint from config by adding
the following in your local.ini
Thanks Alexander.
Is it possible to remove _replicate in the same manner? It occurred to me
that the user could simply
