D
Dominic
Hi there,
My understanding is that I should set cookieless in web.config to
false because many mobile devices do not support cookies. In this way,
ASP.NET will use munged URL for passing session ID. Is that right?
If this is the case, my question is how I can properly bookmark a page
when its URLs contains the session ID? For example, in a certain
session, I enter URL as http://xyz.com/index.aspx. When the page is
loaded, the URL becomes http://xyz.com/(dcdasdf23984)/index.aspx. I
then bookmark this URL. Later, I open a browser and attempt to start a
new session. If I go to this bookmarked URL, it will attempt to go my
previous session because the URL contains the session id of the
previous session. This is, of course, not my intention.
How can I resolve this problem?
For instance, I use Pocket PC emulator. It seems like it can only
allow you to put the current URL to the favorite list. You can't
modify the URL to something like http://xyz.com/index.aspx. It seems
like Openwave browser simulator 6.2.2 behaves similary.
Any idea?
Thanks
Dom
My understanding is that I should set cookieless in web.config to
false because many mobile devices do not support cookies. In this way,
ASP.NET will use munged URL for passing session ID. Is that right?
If this is the case, my question is how I can properly bookmark a page
when its URLs contains the session ID? For example, in a certain
session, I enter URL as http://xyz.com/index.aspx. When the page is
loaded, the URL becomes http://xyz.com/(dcdasdf23984)/index.aspx. I
then bookmark this URL. Later, I open a browser and attempt to start a
new session. If I go to this bookmarked URL, it will attempt to go my
previous session because the URL contains the session id of the
previous session. This is, of course, not my intention.
How can I resolve this problem?
For instance, I use Pocket PC emulator. It seems like it can only
allow you to put the current URL to the favorite list. You can't
modify the URL to something like http://xyz.com/index.aspx. It seems
like Openwave browser simulator 6.2.2 behaves similary.
Any idea?
Thanks
Dom