The following issue was kind of touched in the DNN forum but not explained. May be some of you could tell me why this happens and what to do against it other than deleting cookies.
On my test machine I am running a DNN site and several other .NET 2.0/3.5 websites (which are non-DNN sites). From an IIS standpoint all sites are subsites of the default application meaning all sites are not differentiated by IP, host header or port. They just run as localhost/DNN-site OR localhost/OTHER-site etc.
I am explaining this just to give you an idea about the environment.
SO, when I pull-up localhost/OTHER-site I am getting the ERROR:
A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<profile><item key="...").
MY QUESTION: WHY? Aren't the sites under localhost completely separated because they run as a application with starting-point beneath localhost? Why is the DNN cookie read?
Would that phenomena with the cookies also occur on my production server Win2008 or 2003 where websites certainly do run as a real separate application (meaning not a sub application of the default site like on my test machine)?