In their privacy policy they list the cookie that 'Is essential for their site to function'
"Essential site cookie|ASP.NET_SessionId|This cookie is essential for the online notification form to operate and is set upon your arrival to the ICO site. This cookie is deleted when you close your browser."
They also say that they've left it there because: "as we’re unable to remove it from one part of the site without affecting another"
So apparently incompetence is an excuse for leaving cookies in place. Problem solved!
Does ASP.Net depend on it for some reason? I used to do some work in Java Server Pages, and in JSF we were stuck with something called viewstate, that were kept either as a blob in the page or as reference in the page to a blob stored on the server. Technically not a cookie, but for all intents and purposes the same as a cookie that gets deleted when the browser is closed.
Blocking the cookie lets me view a few pages of the site perfectly fine. I guess the session is required in one small part of the site and it wasn't easy for the developers to make the site only set the cookie in that place.
Comments
In their privacy policy they list the cookie that 'Is essential for their site to function'
"Essential site cookie|ASP.NET_SessionId|This cookie is essential for the online notification form to operate and is set upon your arrival to the ICO site. This cookie is deleted when you close your browser."
They also say that they've left it there because: "as we’re unable to remove it from one part of the site without affecting another"
So apparently incompetence is an excuse for leaving cookies in place. Problem solved!
Does ASP.Net depend on it for some reason? I used to do some work in Java Server Pages, and in JSF we were stuck with something called viewstate, that were kept either as a blob in the page or as reference in the page to a blob stored on the server. Technically not a cookie, but for all intents and purposes the same as a cookie that gets deleted when the browser is closed.
Blocking the cookie lets me view a few pages of the site perfectly fine. I guess the session is required in one small part of the site and it wasn't easy for the developers to make the site only set the cookie in that place.