I work for a large corporation and am in the process of converting a site from classic ASP to ASP.NET 2.0. This is being done on a page by page basis, starting with the homepage, and converting one page at a time over to the newer technology. All in all it is going quite well, however I have run into one snag.
The problem I am running into revolves around a cookie named "ds_edition". Now i have read many posts about classic ASP cookie values being encoded, and having to URL decode them in ASP.NET. That's simple and not my problem. My issue is that the cookie name is being encoded.
response.cookies("ds_edition") writes a cookie that looks like "ds%5Fedition"
Response.Cookies["ds_edition"] writes a cookie that looks like "ds_edition"
Now this isn't a big issue, except when an aspx page has to read a classic asp cookie or the other way around. ASP.NET does not see the "ds%5Fedition" cookie and ASP does not see the "ds_edition" cookie. They hold two seperate values when looking at the cookies in the browser. I have tried all kinds of things to correct the problem and have made no progress. Can anyone shed any light on this? (I k
View Complete Post