Most likely not thought of. The cookieless session is a bit of a kludge to
get around an issue with the stateless nature of web communication coupled
with people turning off cookies in their browsers. I would assume that
bookmarking was not considered when setting up the kludge. I would venture
that setting up your own HTTP Handler may be the only way to get around this
(further kludge the kludge), but it may never let you to that point, as the
intercept is probably before your own handler is called.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************** ********************
Think Outside the Box!
************************************************** ********************
"alex" <al*************@verizon.net> wrote in message
news:%2***************@TK2MSFTNGP09.phx.gbl...
when i bookmark a page in my app with a session id in the path, that
session id doesn't get reset. It survives timeouts, browser and server restarts.
I'm seeing this behaviour whether I use InProc mode or StateServer. I'm
getting this on a remote server where I'm using InProc cookieless mode and I'm
getting this on my local machine where I've tried that and StateServer. I
don't understand why asp.net won't reset the session code and write the
new one to the url.