[
https://issues.apache.org/jira/browse/COUCHDB-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Rempe updated COUCHDB-533:
--------------------------------
Component/s: (was: HTTP Interface)
Administration Console
> When multiple futon views are open, pointing at different couchdb's running
> on different ports, the 'recent databases' section erroneously shows DB's
> across all futons.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-533
> URL: https://issues.apache.org/jira/browse/COUCHDB-533
> Project: CouchDB
> Issue Type: Bug
> Components: Administration Console
> Affects Versions: 0.11
> Reporter: Glenn Rempe
>
> I am running a local CouchDB on localhost:5984. I am also running a
> production CouchDB on a remote host that I am doing SSH port forwarding for
> which I have mapped to localhost:5994. I am accessing their futon instances
> via:
> http://localhost:5984/_utils/status.html
> http://localhost:5994/_utils/status.html
> Viewing the futon for both shows all databases in the 'Recent Databases'
> section, across both instances, in both futons. This is incorrect as each
> futon should only show the subset of DB's that it actually contains.
> e.g.
> http://localhost:5984/_utils/status.html - should only show 'foo_dev'
> http://localhost:5994/_utils/status.html - should only show 'foo_production'
> Clicking on a database that doesn't actually exist results in two javascript
> alerts. The first of which says 'An error occurred retrieving a list of all
> documents: no_db_file'
> Expected behavior:
> Futon should only show databases that exist on the instance being monitored
> in the 'Recent Databases' section.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
