CookieLess Sessions and Bookmarks

[Harolds]

We are currently converting our web site for asp.net 1.1 to asp.net 2.0.
We use cookieless sessions.
We have discovered a problem, when someone using a bookmark set from when
the site was 1.1 they receive the following error:
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make sure that
it is spelled correctly.

Requested URL:
/(n4th2m2frhi3vs3a15xdq2qxS(wnk2dwjrrsd3kmagvrjpa25 5))/home.aspx

The old sessionid (the one in the bookmark) is being appended with the new
sessionid as show in Requested URL:.

What can we do to keeps this from happening?

--
Harolds

[Walter Wang [MSFT]]

Hi Harolds,

Thank you for your post.

I'm afraid this is a known issue of ASP.NET 2.0 as first reported at
http://forums.asp.net/1203148/ShowPost.aspx which also has a workaround
here: http://forums.asp.net/1211205/ShowPost.aspx

If this issue is critical for your product and you don't want to use the
workaround, you may contact MSDN representatives to submit your questions
online or through phone:
http://msdn.microsoft.com/subscripti...t/default.aspx
As an MSDN Subscriber, you are entitled to receive up to four support
incidents depending on your subscription level.

Please feel free to post here if anything is unclear.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Harolds]

Thanks
--
Harolds
"Walter Wang [MSFT]" wrote:

Hi Harolds,

Thank you for your post.

I'm afraid this is a known issue of ASP.NET 2.0 as first reported at
http://forums.asp.net/1203148/ShowPost.aspx which also has a workaround
here: http://forums.asp.net/1211205/ShowPost.aspx

If this issue is critical for your product and you don't want to use the
workaround, you may contact MSDN representatives to submit your questions
online or through phone:
http://msdn.microsoft.com/subscripti...t/default.aspx
As an MSDN Subscriber, you are entitled to receive up to four support
incidents depending on your subscription level.

Please feel free to post here if anything is unclear.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Harolds,

Thank you for your update. Please feel free to post here if you need more
help on this.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.