[
https://issues.apache.org/jira/browse/COUCHDB-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin updated COUCHDB-2116:
--------------------------------------
Description:
1. Have a server with Admin Party
2. Open two tabs with Futon and Fauxton
3. Fix admin party in Futon
4. Navigate thought pages on Fauxton - Admin Party is still there
5. Try to refresh Fauxton tab - still Admin party
6. Close Fauxton tab and open it again - finally fixed!
7. Logout and login on Futon - Fauxton still thinks that you're anonymous
8. Ok, let's login on Fauxton too. And remove all admins from config
9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still logged
in.
Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon -
you're logged in without any issues.
UPDATE. Another case:
1. Navigate to databases list page
2. Create new database
3. Go back (no matter how: via browser history, by click on sidebar link)
4. You'll miss that database in the list
Same is true if you delete database - nothing changes in the list even if you
change the view page, refresh the tab or open the new one.
However, after ~one minute Fauxton will show the changes. I believe that both
cases are happens because of local state caching which doesn't reacts on
changes that current user made.
was:
1. Have a server with Admin Party
2. Open two tabs with Futon and Fauxton
3. Fix admin party in Futon
4. Navigate thought pages on Fauxton - Admin Party is still there
5. Try to refresh Fauxton tab - still Admin party
6. Close Fauxton tab and open it again - finally fixed!
7. Logout and login on Futon - Fauxton still thinks that you're anonymous
8. Ok, let's login on Fauxton too. And remove all admins from config
9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still logged
in.
Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon -
you're logged in without any issues.
Summary: Fauxton cache is too persistent (was: Fauxton auth is too
persistent)
> Fauxton cache is too persistent
> -------------------------------
>
> Key: COUCHDB-2116
> URL: https://issues.apache.org/jira/browse/COUCHDB-2116
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Fauxton
> Reporter: Alexander Shorin
>
> 1. Have a server with Admin Party
> 2. Open two tabs with Futon and Fauxton
> 3. Fix admin party in Futon
> 4. Navigate thought pages on Fauxton - Admin Party is still there
> 5. Try to refresh Fauxton tab - still Admin party
> 6. Close Fauxton tab and open it again - finally fixed!
> 7. Logout and login on Futon - Fauxton still thinks that you're anonymous
> 8. Ok, let's login on Fauxton too. And remove all admins from config
> 9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still
> logged in.
> Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon
> - you're logged in without any issues.
> UPDATE. Another case:
> 1. Navigate to databases list page
> 2. Create new database
> 3. Go back (no matter how: via browser history, by click on sidebar link)
> 4. You'll miss that database in the list
> Same is true if you delete database - nothing changes in the list even if you
> change the view page, refresh the tab or open the new one.
> However, after ~one minute Fauxton will show the changes. I believe that both
> cases are happens because of local state caching which doesn't reacts on
> changes that current user made.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
