couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Kocoloski <>
Subject Re: Difficulty replicating behind a proxy server
Date Fri, 15 Dec 2017 13:22:02 GMT
Thanks. If you’re interested in poking around the codebase I think the place where one could
bypass the proxy URL for localhost addresses is here:

Cheers, Adam

> On Dec 14, 2017, at 11:25 PM, Jake Kroon <> wrote:
> Hi Adam,
> Thank you very much for the prompt feedback. At the nearest convenience I will raise
an issue at
> We will also have a look into whether we can potentially implement a fix for this issue.
> Thanks again,
> Jake Kroon
> On 2017-12-14 05:57, Adam Kocoloski <> wrote:
>> Hi Jake, ugh, yes, I think you?019ve hit the nail on the head. In your first configuration,
CouchDB is seeing an HTTP-based target and assuming it needs to use the proxy. Your second
configuration fails because the replicator does not yet work with local clustered databases.>
>> I think the quickest fix here is to add a check for localhost URLs and not use the
proxy for those. Can you file an issue at ?>
>> Thanks, Adam>
>>> On Dec 12, 2017, at 11:44 PM, Jake Kroon <>
>>> Hi,>
>>> We are experiencing issues when running CouchDB 2.0.0 behind a proxy, specifically
when trying to perform replication. When performing replication without a proxy we do not
experience any issues. We're attempting to start the replication by adding a document to the
/_replicator/ database, but as you can see below, it changes to an error state with an "invalid
json" error:>
>>> {>
>>> "_id": "rep_init",>
>>> "_rev": "20-81f3b1999b7f8e9ac51a45e3acbc4432",>
>>> "source": "https://<username>:<password>@dbgateway.<domain>.com/<source_db_name>",>
>>> "target": "<targe

View raw message