Duplicate Session ID

[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?

[ashelley]

On Mon, 28 Jun 2004 15:35:43 -0700, "Marcio Kleemann" <notavailable>
wrote:

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?

This is a known behaviour. On the web u can easily open instances of
browsers in the same session (IE ctrl+n and as you have shown, a
shortcut). You can't guarantee people will hop onto new sessions and
this will have to be programmed around.

-adam

[Marcio Kleemann]

I was not aware of that, but if this is "normal" behavior, how would you
determine that a new browser instance is actually duplicating a session
instead of starting a new session? Can you suggest how that would be
programmed around?

Thanks

<as******@inlandkwpp.com> wrote in message
news:qg********************************@4ax.com...

On Mon, 28 Jun 2004 15:35:43 -0700, "Marcio Kleemann" <notavailable>
wrote:

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 (whichruns locally on IIS under XP Pro). If I use the shortcut more than once tobring 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 doget separate session IDs as expected. But as soon as I use a shortcut, thepages displayed by the browser all report the same session ID.

Anyone run across this before? Does anyone understand what is happening
here?

This is a known behaviour. On the web u can easily open instances of
browsers in the same session (IE ctrl+n and as you have shown, a
shortcut). You can't guarantee people will hop onto new sessions and
this will have to be programmed around.

-adam