We have several clients that can no longer access out site because they are behind MS Proxy 2.0. This happened as a direct result of our upgrade to ASP.NET 2.0. We are using the cookieless approach with session ID in the URL. Has anybody had any experience with this?

Chip

Hi Chip,

I haven't heard of this issue before, but am forwarding it onto people to investigate.

Thanks,

Scott

When users can't access the site - what are they getting back in their browser - a 404 error?  There is a bug in the 2.0 cookieless session state implementation where we do not properly handle old ASP.NET 1.1 style cookieless identifiers.  Is it possible that the proxy servers for these users has cached the old 1.1 style identifiers - thus causing errors when they attempt to access the site?

Hi, i have a similar problem.

We have a wap site that uses cookieless state management. If i enable cookies in session management so everything goes fine but many cell phones do not support cookies so it is a must for us to use cookieless session state. 

We are running  ipfw firewall and natd demon on FreeBsd and our users have the same problem. They are getting 404 file not found error page.

 Is there any workaround or patch for this problem so far ?