It would have made more sense to have a tag, but it is no simple task to add a new tag to the HTML specification and then to get it supported in 1.2 million different versions of user agents. It should be pretty obvious that this behavior is really stretching the intended purpose of the tag, which is why there are so many fields being overloaded into the content attribute. However, to complete the requirement for the session expiration page, we need to send the user's browser to a new page, in this case /SessionExpired.aspx which is set with the url= string within the content attribute. The syntax for the META tag, when used for this purpose, is pretty simple. The simplest way to implement a cross-browser session expiration page is to add a META tag to the HTML headers of any pages that require authentication and/or a valid session. At least with this solution, the user immediately knows his session has ended, and he can re-initiate it and continue his work without any loss of time. The user may still lose some work he was in the middle of on the page he was on, but that would have been lost anyway had he tried to submit it while no longer authenticated. One way to alleviate this user interface annoyance is to automatically redirect the user to a "session expired" page once their session has expired. Often, the user may begin entering data into a large form, switch to some other more pressing task, then return to complete the form only to find that his session has expired and he has wasted his time. In many applications, an authenticated user's session expires after a set amount of time, after which the user must log back into the system to continue using the application.
0 kommentar(er)
