You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by fana <fa...@2flub.org> on 2009/06/27 19:31:46 UTC
Different database content when accessing CouchDB through localhost or
public IP
Hi,
I'm using CouchDB 0.8 which ships with Debian Lenny.
When I first played around with CouchDB I configured
it to listen on my server's public IP and today I switched it back to
listen on localhost.
But when I browsed the database now, it showed me documents
which were not showed when I used Futon through the public IP.
There is no cache or reverse proxy between me and my server.
Is this by design?
Re: Different database content when accessing CouchDB through
localhost or public IP
Posted by Randall Leeds <ra...@gmail.com>.
Could you possibly be running two CouchDB instances by accident?
On Sun, Jun 26, 2011 at 23:34, yayati <op...@gmail.com> wrote:
> Noah Slater <ns...@...> writes:
>
>> There must be something else going on. CouchDB does not alter its behaviour
>> depending on the IP or port number it binds to. Perhaps someone else added this
>> documents without your knowledge?
>>
>> Best,
>>
>
>
> I see the same problem with couchDB 0.11.0 on debian squeeze
>
>
Re: Different database content when accessing CouchDB through localhost or public IP
Posted by yayati <op...@gmail.com>.
Noah Slater <ns...@...> writes:
> There must be something else going on. CouchDB does not alter its behaviour
> depending on the IP or port number it binds to. Perhaps someone else added this
> documents without your knowledge?
>
> Best,
>
I see the same problem with couchDB 0.11.0 on debian squeeze
Re: Different database content when accessing CouchDB through
localhost or public IP
Posted by Noah Slater <ns...@apache.org>.
On Sat, Jun 27, 2009 at 07:31:46PM +0200, fana wrote:
> But when I browsed the database now, it showed me documents
> which were not showed when I used Futon through the public IP.
>
> There is no cache or reverse proxy between me and my server.
There must be something else going on. CouchDB does not alter its behaviour
depending on the IP or port number it binds to. Perhaps someone else added this
documents without your knowledge?
Best,
--
Noah Slater, http://tumbolia.org/nslater