[
https://issues.apache.org/jira/browse/WAVE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032322#comment-13032322
]
David Hearnden commented on WAVE-196:
-------------------------------------
I'm unable to reproduce also.
I've tried doing the same thing I did when I filed this bug, and things appear
to behave correctly now.
I'm not entirely confident that the problem has been fixed, because AFAIK
nobody's looked into how we're setting cache headers since I filed this bug,
and if we're returning pages that are marked as cacheable, then it is possibly
that an intermediate web proxy may deliver user A's pages to user B.
But if nobody can reproduce, it's not worth keeping this open. Switching to
https may also obviate this issue.
> Logout does not work
> --------------------
>
> Key: WAVE-196
> URL: https://issues.apache.org/jira/browse/WAVE-196
> Project: Wave
> Issue Type: Bug
> Assignee: Michael MacFadden
> Priority: Minor
>
> <b>What steps will reproduce the problem?</b>
> 1. Log in to a WIAB server, with fake or memory accounts.
> 2. Click logout
> Expected: Return to login screen. Refreshing earlier pages should all
> redirect to login screen.
> Actual: No effect. After clicking logout, the client reloads.
> Authentication appears to succeed against all URLs, using old credentials.
> ---
> Issue imported from
> http://code.google.com/p/wave-protocol/issues/detail?id=195
> Label: Type-Defect
> Label: Priority-Medium
> Stars: 1
> State: open
> Status: New
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
