M
Marcio Kleemann
I've run across some very strange behavior when running and debugging an
asp.net application. I have created a shortcut to the URL of the app (which
runs locally on IIS under XP Pro). If I use the shortcut more than once to
bring up two or more browser windows for that page, the Session ID is the
same for all those windows. If I leave those windows open, then
independently launch the browser and enter the URL, I do get a brand new
session. It seems to be related just to the shortcut, because I can open
multiple browser windows, and then key in the URL on each of them, and I do
get separate session IDs as expected. But as soon as I use a shortcut, the
pages displayed by the browser all report the same session ID.
Anyone run across this before? Does anyone understand what is happening
here?
asp.net application. I have created a shortcut to the URL of the app (which
runs locally on IIS under XP Pro). If I use the shortcut more than once to
bring up two or more browser windows for that page, the Session ID is the
same for all those windows. If I leave those windows open, then
independently launch the browser and enter the URL, I do get a brand new
session. It seems to be related just to the shortcut, because I can open
multiple browser windows, and then key in the URL on each of them, and I do
get separate session IDs as expected. But as soon as I use a shortcut, the
pages displayed by the browser all report the same session ID.
Anyone run across this before? Does anyone understand what is happening
here?