- May 18, 2001
- 7,881
- 378
- 126
I'm not a web application programmer, but I sometimes pretend to be one at work. So if the following makes no sense, please ask questions and I'll try to answer them to the best of my ability.
I wrote an ASP web application for PocketPC. The default page of the web app is stored in such a way on one of our servers so that the user has to authenticate themselves (userid & password) before they are allowed access to the web app. This is exactly how I want this application to work, and this is how it works 90% or more of the time.
The problem is that apparently PocketPC is storing information about the logged on user somewhere; my first guess is that this information is being stored as cached pages. I have put code in my ASP program to prevent page caching, but it doesn't seem to work. This might be because Pocket Internet Explorer is equivalent to Internet Explorer 3.0, and may not support options to block caching. So I wrote a VC++ program that resides in the startup folder of the device, to be run when the PocketPC is cycled. This application deletes the entire contents of "windows\temporary internet files", which seems to be where PocketPC caches pages. Also, in my web app, when the user hits a "logoff" button, I have code that cycles the PocketPC. In theory every time the user logs off, the PocketPC cycles itself, runs my VC++ app and clears out any cached web pages.
It seems that this doesn't work all the time. Every now and again the user is allowed access to the web app without having to authenticate themselves. They are immediately presented with pages that are obviously cached because they contain the text string that is the name of the previous logged-in user.
Any suggestions?
I wrote an ASP web application for PocketPC. The default page of the web app is stored in such a way on one of our servers so that the user has to authenticate themselves (userid & password) before they are allowed access to the web app. This is exactly how I want this application to work, and this is how it works 90% or more of the time.
The problem is that apparently PocketPC is storing information about the logged on user somewhere; my first guess is that this information is being stored as cached pages. I have put code in my ASP program to prevent page caching, but it doesn't seem to work. This might be because Pocket Internet Explorer is equivalent to Internet Explorer 3.0, and may not support options to block caching. So I wrote a VC++ program that resides in the startup folder of the device, to be run when the PocketPC is cycled. This application deletes the entire contents of "windows\temporary internet files", which seems to be where PocketPC caches pages. Also, in my web app, when the user hits a "logoff" button, I have code that cycles the PocketPC. In theory every time the user logs off, the PocketPC cycles itself, runs my VC++ app and clears out any cached web pages.
It seems that this doesn't work all the time. Every now and again the user is allowed access to the web app without having to authenticate themselves. They are immediately presented with pages that are obviously cached because they contain the text string that is the name of the previous logged-in user.
Any suggestions?
Facebook
Twitter