Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 821ABF677 for ; Fri, 12 Apr 2013 03:15:19 +0000 (UTC) Received: (qmail 63472 invoked by uid 500); 12 Apr 2013 03:15:18 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 63336 invoked by uid 500); 12 Apr 2013 03:15:17 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 63161 invoked by uid 99); 12 Apr 2013 03:15:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 03:15:17 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stemail23@gmail.com designates 209.85.220.42 as permitted sender) Received: from [209.85.220.42] (HELO mail-pa0-f42.google.com) (209.85.220.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 03:15:11 +0000 Received: by mail-pa0-f42.google.com with SMTP id kq13so1221674pab.29 for ; Thu, 11 Apr 2013 20:14:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=uQuMyaBnfhJkWO6uxz45y0V9+l97hziEBWqtHxYz+nE=; b=uH4Fh1H8pdqxG2wM10QdjwdrRSOU1sJzGfeYbAw1gzVAvswyuRJ6pxexc45j5iROca MD8IHSt0l04FuDAHzDaeJ/gIKbinjwD3bIobjWMAwn4lVokkkQUv6d7Kpp4bfi80ZqZd gZQQ2dpwK2m6Oi8bRRiIZz0JvGRcbiu2b2pJ7BFyk490tK30mTwDynIU0IKHjngqkLFc 3BqHal4L8/lQn/mpvukT7tcVR3TGmVQ5bt/3WSzAGGHZq2YpyvbJ8Fk65KDbWCw8Swk5 oLGzA1Iimlw+9KJ6+4R8O/1HL3XJNCSzb8u2OxkjKlw+ZmIE8DO75sGRxFD7WLAxRoEr bE3g== MIME-Version: 1.0 X-Received: by 10.66.231.5 with SMTP id tc5mr12964682pac.144.1365736490068; Thu, 11 Apr 2013 20:14:50 -0700 (PDT) Received: by 10.66.159.73 with HTTP; Thu, 11 Apr 2013 20:14:50 -0700 (PDT) Date: Fri, 12 Apr 2013 13:14:50 +1000 Message-ID: Subject: _replicator database and proxies From: Steven To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=047d7b15ab2958f5ed04da214e77 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b15ab2958f5ed04da214e77 Content-Type: text/plain; charset=ISO-8859-1 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. --047d7b15ab2958f5ed04da214e77--