[
https://issues.apache.org/jira/browse/OLIO-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682078#action_12682078
]
William Sobel commented on OLIO-69:
-----------------------------------
I'll check into this issue and see if I can reproduce. I don't see why the app
should be left in an inconsistent state. The only information in the cookie is
a single signed token representing your user id. If the signature get
corrupted, the application will not let you access since it believes you are
trying to hack it.
Why does the the rails server need to be bounced when you kill?
> Killing a run leaves the application in an inconsistent state.
> --------------------------------------------------------------
>
> Key: OLIO-69
> URL: https://issues.apache.org/jira/browse/OLIO-69
> Project: Olio
> Issue Type: Bug
> Components: rails-app
> Environment: probably not environment related. I'm running ruby
> 187p72 and rails 2.1.0 on opensolaris.
> Reporter: Prashant Srinivasan
> Assignee: Shanti Subramanyam
> Priority: Minor
>
> If I kill a run before it completes, and access the application through a
> browser where I'm currently logged in, the application will not let me log
> out, log in, or register.
> I don't think that this is a use case that we want to support, but Im filing
> the issue so that others can comment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
