|
Don't
rely on user variables being there. They may be there, but will probably be
inaccessible.
Do you
have your log turned on? Do you see anything in the log about it being
triggered?
A good
test is to copy and paste (but not execute) the URL into a browser and
then wait until you know for a fact that user session should have timed out and
_then_ execute the variabletimeouttrigger URL. That should give you exactly what
should happen.
-----Original Message-----
From: Trevor Green [mailto:[EMAIL PROTECTED] Sent: September 18, 2003 6:10 AM To: Multiple recipients of list witango-talk Subject: Witango-Talk: variabletimeouttrigger
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf |
- Witango-Talk: Encoding bug? Ezra
- Re: Witango-Talk: Encoding bug? Robert Shubert
- RE: Witango-Talk: variableTimeoutTrigg... Two 2 Witango
- Re: Witango-Talk: variableTimeoutT... John McGowan
- RE: Witango-Talk: variableTime... Two 2 Witango
- Witango-Talk: DBMS action Ted Wolfley
- RE: Witango-Talk: DBM... Ben Johansen
- RE: Witango-Talk:... Ben Johansen
- Re: Witango-Talk: variableTimeoutTrigger ServerSmiths Tango Development
- Witango-Talk: variabletimeouttrigger Trevor Green
- Witango-Talk: variableTimeoutTrigger Kevin Quinn
- Witango-Talk: variableTimeoutTrigger Roland A . Dumas
- Witango-Talk: variableTimeoutTrigger David Green
- Re: Witango-Talk: variableTimeoutTrigg... Roland Dumas
- Re: Witango-Talk: variableTimeoutT... isabelle
- Re: Witango-Talk: variableTimeoutT... ServerSmiths Tango Development
- Re: Witango-Talk: variableTimeoutTrigger Bill Conlon
- Re: Witango-Talk: variableTimeoutTrigg... David Green
- Re: Witango-Talk: variableTimeoutT... witango man
