Right, lets take a step back, ok?<BR><BR>HTTP client/server model and ASP:<BR>1) Client makes request.<BR>2) Server receives request.<BR>3) If no session is started for this client, fire session_onstart in global.asa<BR>4) Execute ASP page client requested.<BR>5) Return data<BR><BR>Although the request object is AVAILABLE from within the global.asa file, can you really guarantee that the request.form collection will be populated? That would only happen on the off-chance that someone submitted a form from a different server to yours, and they didn't have an existing session on your server.<BR><BR>Which "login/pass" are you after? I think this isn't the right way to approach the problem.<BR><BR>Craig.
I have a password protected site. <BR>I have a problem. Problem is that with one login/password more then one user can connect to site at a time. I want with one login/password only one user can connect to site at a time <BR>How can i solve this problem <BR><BR>i want to use<BR>session_onstart then user try to login<BR>and session_onend when userlogut.<BR><BR>to keep track of users<BR>
This is a very common problem, and one that's actually very hard to solve. Session_OnEnd is buggy - it's not always called, and I've heard that you also cannot use database access inside it.<BR><BR>I suggest you re-evaluate the situation - is there a different way that you could keep track of the users?<BR><BR>Craig.