Problem ID: 3629989844290161074
Entered by: Ben Simo

What do you want me to do?

I got this error trying to sign into a web site. I had last signed into the web site about 17 hours prior to getting this error message. What is this message telling me?

Is it saying that I signed in too soon? If so, how much longer than 17 hours do I have to wait?

Is it saying that my browser can have cookie issues that are capable of forcing me to do things too soon?

Is it saying my browser is doing things on its own because of cookie issues?

Or maybe this message is telling me what to do.

Is it saying that I should sign in again too soon? If so, how soon is too soon. And if it is too soon, why should I do it?

Seriously, I doubt this message is at all related to the actual problem. The message makes no sense. This is the kind of message that makes we wonder why some coder spent time entering the error message text into a computer.

And now I'm cringing at the thought that I may have -- sometime in the distant past -- written error messages that are just as confusing.

Pressing the back button and resubmitting the login resulted in the same error. However, I then closed the browser tab and re-clicked the link that led me to login to the site. This time I was not prompted to login. I was sent directly to the destination page that requires user authentication.

It appears my browser had the appropriate session cookies.



June 17, 2009 at 10:54 PM  
Comment ID: 3638673146958099461
Written by: Anonymous

Sure there is a problem, What i feel is there should be a message telling user about session time out and the login page should be displayed.

June 17, 2009 at 11:43 PM  
Comment ID: 5619410675843567592
Written by: Ben Simo

This page came in response to a login. So, in my opinion, a user should not see any messages about timeouts.

June 19, 2009 at 9:32 AM  
Comment ID: 8947636625029564974
Written by: neochance

The problem is that most error messages (like the one above) are written to communicate something relevant about the issue at hand to the developer instead of to the customer.

Post a Comment