I have an isapi filter written in C. Its only purpose is to set a cookie (using AddResponseHeaders function) on every request when the IIS
SF_NOTIFY_AUTH_COMPLETE notification occurs. Also, on this web server I have an asp.net application that, from a simple button click handler, sets the same exact cookie with a different value. This means that on the postback request when a user clicks the asp.net button, the 2 cookies are set.
Now the problem. On IIS 6, the cookie set by the asp.net application has precedence and the client browser keeps the correct value coming from the asp.net app. This is the desired behavior (on such requests, I can see in the response headers that the asp.net application cookie comes after the isapi one). Now I'm moving this setup on IIS 7.5 and I see the opposite, the isapi cookie has precedence and the client gets the wrong value after the asp.net button click.
I saw simmilar post http://forums.iis.net/p/1201241/2057284.aspx?Re+ISAPI+filter+in+IIS+7+5+has+a+different+behavior+than+IIS+6 but couldn't find the soultion for that.
Anyone can shed some light on these interrogations?