incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: _replicator database and proxies
Date Wed, 24 Apr 2013 13:42:20 GMT
Q: "Why is the proxy configuration part of the replication document at all?

A: Because each replication document is an independent entity.

Making it global works for your case but not the general case. Why is
your proxy configuration changing so rapidly?


On 24 April 2013 08:31, Steven <> wrote:
> OK, please excuse the bump, but really? No takers on this one?
> I'm surprised if I'm the only person encountering this situation. Is nobody
> else working on a system with replication to laptop devices that use
> multiple connections?
> Here's my biggest confusion: Why is the proxy configuration part of the
> replication document at all? Surely a global proxy setting would make way
> more sense, otherwise, the only way I can see around this issue is to tear
> down the entire replication database document set, and rebuild it when I
> detect a change in proxy configuration. That seems like madness!
> Any comments appreciated.
> Cheers.
> On Fri, Apr 12, 2013 at 1:14 PM, Steven <> wrote:
>> Question about using the _replicator database to set up persistent
>> replications from a machine that uses various different connections,
>> sometimes behind a proxy, other times not.
>> Question is: Given that the proxy server information is part of the
>> replication document, the replication breaks (returns an error) when the
>> connection changes to use a different, or no, proxy. How am I supposed to
>> handle this situation?
>> Also, an observation: when the replication document contains "proxy": null
>> (in V1.3), the replication fails, this caught me out for a while, the
>> replication document proxy parameter must be entirely absent to specify no
>> proxy.

View raw message