jjw wrote on 31 aug 2006 in microsoft.publi c.inetserver.as p.general:
>
Evertjan. wrote:
>Ray Costanzo [MVP] wrote on 29 aug 2006 in
microsoft.publ ic.inetserver.a sp.general:
The only feasible way to do this would be to kick everyone out by
restarting the app and killing all the sessions. Something else to
look into is storing the login status in a database instead of using
sessions.
Start each user page with:
if application("ki llAll") = "do" then session.abandon :response.end
kill.asp [only with password]:
application("k illAll") = "do"
unkill.asp [when used after the session timeout time]:
application("k illAll") = "notSo"
Would this work?
thanks for your reply. that would work, and I kinda thought of
something like that, but your way implements it a bit better. anyway,
the only bad part is I'd have to add it to each and every page, but
that's probably what I'll be doing.
There is a minor(!) problem with this:
If a user "refreshes" the session by calling a non-asp file,
like .jpg, .pdf, .html, repeatedly, I suppose that session could
be left intact when running unkill after 20 minutes.
If this flaw bothers you,
perhaps you would have to use an incrementing "killLevel" number:
Start each user page with:
if session("killal l") = "" then
session("killal l") = application("ki llAll")
end if
if application("ki llAll") session("killal l") then
session.abandon
response.end
end if
This will set to self-kill all sessions
that are "old" when you increase this killall level with:
kill.asp [only with password]:
application("ki llAll") = application("ki llAll") + 1
and in global.asa application onstart:
application("ki llall") = 0
[no unkill in this scheme]
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
