Getting rid of session cookie ("ASP.NET_Sessi onId")

[Daniel Michaeloff]

Hi all,

I have an application that when finished redirects to a non-ASP.NET app
which is choking on a huge ASP.NET session cookie. The cookie
"ASP.NET_Sessio nId" gets transmitted by the browser (IE6 in test case)
despite trying Microsoft's suggested method of expiring the cookie first.

I'd like to be able to kill the cookie and do a Response.Redire ct() from
within a server-side button handler, but I'm to the point now where I'm
instead redirecting to a third .aspx page whose only job is to remove the
cookie and have a hyperlink out. In its Page_Load:

{
System.Web.Http Context.Current .Session.Abando n();

HttpCookieColle ction cookieColl = HttpContext.Cur rent.Request.Co okies;
String[] names = cookieColl.AllK eys;
System.Web.Http Context.Current .Trace.Write(St ring.Format("{0 } cookies:",
names.Length));
for (int i = 0; i < names.Length; i++) {
HttpCookie cookie = cookieColl[names[i]];
System.Web.Http Context.Current .Trace.Write(St ring.Format(" {0}",
names[i]));
cookie.Expires = DateTime.Now.Ad dDays(-1);
cookie.Domain = "invaliddomain" ;
cookie.Path = "invalidpat h";
cookie.Value = "invalidval ue";
Response.Cookie s.Add(cookie);
}
}

.... but on clicking the hyperlink, the cookie yet lives.

Any ideas? Is this something specific to IE6 perhaps, some security update
that special-cases ASP.NET cookies? Any help is appreciated.

Thanks,
--Dan Michaeloff

[Hans Kesting]

Daniel Michaeloff wrote:

Hi all,

I have an application that when finished redirects to a non-ASP.NET
app which is choking on a huge ASP.NET session cookie. The cookie
"ASP.NET_Sessio nId" gets transmitted by the browser (IE6 in test case)
despite trying Microsoft's suggested method of expiring the cookie
first.

I'd like to be able to kill the cookie and do a Response.Redire ct()
from within a server-side button handler, but I'm to the point now
where I'm instead redirecting to a third .aspx page whose only job is
to remove the cookie and have a hyperlink out. In its Page_Load:

{
System.Web.Http Context.Current .Session.Abando n();

HttpCookieColle ction cookieColl =
HttpContext.Cur rent.Request.Co okies; String[] names =
cookieColl.AllK eys;
System.Web.Http Context.Current .Trace.Write(St ring.Format("{0 }
cookies:", names.Length)); for (int i = 0; i < names.Length; i++) {
HttpCookie cookie = cookieColl[names[i]];
System.Web.Http Context.Current .Trace.Write(St ring.Format("
{0}", names[i]));
cookie.Expires = DateTime.Now.Ad dDays(-1);
cookie.Domain = "invaliddomain" ;
cookie.Path = "invalidpat h";
cookie.Value = "invalidval ue";
Response.Cookie s.Add(cookie);
}
}

... but on clicking the hyperlink, the cookie yet lives.

Any ideas? Is this something specific to IE6 perhaps, some security
update that special-cases ASP.NET cookies? Any help is appreciated.

Thanks,
--Dan Michaeloff

What probably happens is that the ASP.Net system automatically
adds that cookie, overwriting your "remove this cookie" version.

Try adding a "EnableSessionS tate=False" to the @ Page directive in the aspx,
maybe this will get rid of the new session cookie.

Hans Kesting