Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <4DEFDE9B.3020502@gmail.com>
References: <4DEFDE9B.3020502@gmail.com>
Date: Wed, 8 Jun 2011 21:46:50 +0100
Message-ID: <BANLkTim+rqEidwF=j6cGW9vVceysLww1Pw@mail.gmail.com>
Subject: Re: problem with replication through proxy
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The replicator is looking for a checkpoint. It's perfectly ok if it
doesn't find one, though.

I suspect Apache is returning its own 404 message (and response body)
instead of the one that couchdb sends, and that the replicator is
expecting. Disable the error page handling and have another try.

B.

On 8 June 2011 21:42, Kevin R. Coombes <kevin.r.coombes@gmail.com> wrote:
> Hi,
>
> We have a setup with CouchDB running behind an Apache proxy, and are havi=
ng
> trouble replicating from the proxy to an outside server. =A0Basically, yo=
u can
> imagine the following setup:
>
> Proxy Server: =A0http://public.proxy.wherever.com
> =A0 =A0which forwards GET requests (but not PUT, POST, or DELETE) to
> CouchDB server: =A0http://internal.couch.wherever.com:5984
> =A0 =A0and we want to replicate this database to
> New CouchDB Server: http://somewhere.else.com:5984
>
> We started by creating a new empty database ('newdb') on the new server; =
it
> contains absolutely no documents. =A0We then POST a replicaton request to=
 the
> new server in the form
>
> curl -X POST http://somewhere.else.com:5984/_replicate -d
> '{"source":"http://public.proxy.wherever.com/ourdb",
> "target":"http://somewhere.else.com:5984/newdb"}'
>
> The error message we get has the form
> =A0 =A0The requested URL
> =A0 =A0 =A0 =A0/ourdb/_local/8262b7d6670639f25400d5940bbe4094
> =A0 =A0was not found on this server.
>
> We cannot figure out what it is looking for (since it does not exist on t=
he
> server...) =A0And so we cannot tell if this is a problem with the
> configuration of the proxy server or if it is something about our particu=
lar
> database. =A0As far as we can tell, none of the documents in the original
> couch database has an _id that looks anything like this. =A0(We assigned =
all
> of the _id's manually, since there is a good semantic reason to assign
> meaningful unique _id's in our application.)
>
> Can anyone point us in the right direction to resolve this problem?
>
> Thanks,
> =A0 =A0Kevin
>
>
>