In order for the Auth object to function properly it is important that the server name stays exactly the same (including capitalization). This is because Web browsers only send cookies back to the server that originally sent them. If you call the page
http://www.FoxWeb.com/test.fwx, get authenticated and follow a link to
http://www.foxweb.com/test.fwx, you will be asked to enter your user id and password again. This is why we recommend that you always use relative instead of fully qualified URLs.
Another possible reason would be if your various pages use a different combination of Auth.AuthList and Auth.AuthTable. If two pages populate one or both of these properties differently, then they will not allow a user to access both with a single login.
These may or may not be the cause of the problem, but it's a good place to start. Try comparing Session.GetSessionID, Auth.AuthList and Auth.AuthTable between hits to determine where the problem lies.
FoxWeb Support Team
support@foxweb.com
Sent by Curtis Hertwig on 10/31/2001 07:59:46 AM:
I have users complaining of being timed out too quickly.
In certain circumstances (not all the time, but I can't figure out what the difference is), I am required to log back in and from then forward on every page change. It seems to authenticate me for that page, but has to re-authenticate me on every page unless I restart IE.
Any ideas?