Issue Details (XML | Word | Printable)

Key: GALAXY-245
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Andrew Perepelytsya
Reporter: Todd Wells
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Galaxy

Session timeout caues undesirable results in web UI

Created: 07/May/08 04:19 PM   Updated: 03/Jun/08 09:23 AM
Component/s: Web
Affects Version/s: 1.0-beta-3
Fix Version/s: 1.0-RC

Time Tracking:
Not Specified

Issue Links:
Related
 

Labels:
User impact: High


 Description  « Hide
If your session times out in the web UI, when you attempt to use it again, it will attempt to navigate to whatever section you select, but will then display an ugly error box on the screen that says this (yes, it's unrendered HTML):

Error communicating with server: <html> <head> <title>Mule Galaxy Login</title> <link type="text/css" rel="stylesheet" href="login.css" /> </head> <body> <div id="body"> <form action="./j_acegi_security_check" method="post"> <div class="loginBox"> <div class="loginTop"><img src="images/galaxy_small_logo.png" style="float: right; margin-top: 1px; " border="0"/></div> <div class="loginLeft"></div> <div class="loginRight"> <div class="loginContent"> <div class="label"> Username: <input name="j_username" value="" /> </div> <div class="label"> Password: <input name="j_password" type="password" value="" /> </div> <div class="loginButton"> <input type="submit" value="Login" /> </div> </div> </div> <div class="loginBottom"> Powered by MuleSource </div> </div> </form> </div> </body> </html>

It should detect that the session has expired and return you to the logon screen. You will get different but similar errors like this as you attempt to navigate around, but you won't return to the logon screen until you hit Refresh.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Andrew Perepelytsya added a comment - 07/May/08 04:22 PM
Actually, I've been on this issue for some time. The problem is more complex, as this is not a simple session timeout of the page, but rather an ajax request which has to detect this.

Andrew Perepelytsya added a comment - 08/May/08 06:59 PM