IIS7 - Known Issues and Workarounds

Re: IIS7 Response.Cookies Collection is Empty

Glenn Slayden — Tue, 08 Sep 2009 22:43:03 GMT

CooperNYC:
Response.Headers does seem to work, but I can only see ONE of the cookies (not all three). The Response.AppendHeader method will not work as I need to READ the cookies using the HttpModule, not write additional cookies.

This is exactly the problem I'm having, as I just posted about at http://forums.iis.net/p/1102533/1815781.aspx#1815781 . What's going on with this long-standing issue?

Note that the hotfix KB932385 does *not* fix this issue, it only ensures that the additional cookies are passed to the client browser, but the server-side Resonse object still does not show them in the Headers property.

Poking around with the debugger, I couldn't find those cookies (which do end up at the browser) in any internal or public data structure on the server.

Re: IIS7 Response.Cookies Collection is Empty

CooperNYC — Mon, 04 Aug 2008 19:46:04 GMT

KJ: The test case I am using is a classic ASP page that sets 3 cookies in the HTTP response. The managed HttpModule is not able to read them later in the pipeline (on the same response...the cookie collection is empty). I'm not sure if setting them from Classic ASP code counts as "Native".

Response.Headers does seem to work, but I can only see ONE of the cookies (not all three). The Response.AppendHeader method will not work as I need to READ the cookies using the HttpModule, not write additional cookies.

Re: IIS7 Response.Cookies Collection is Empty

ksingla — Sat, 02 Aug 2008 18:35:24 GMT

Hi Cooper,

1. Can you pls confirm that when you set the Set-Cookie header in native code, Set-Cookie header value as read by Response.Headers in managed code is updated?

2. I am not sure how Response.Headers behave but can you also try Response.AppendHeader method and see if that gives you what you want.

Thanks,
Kj

Re: IIS7 Response.Cookies Collection is Empty

CooperNYC — Fri, 01 Aug 2008 14:15:14 GMT

Thanks KJ. I have tried almost every event in the pipeline with no luck. I also brought this issue up in the IIS7/ClassicASP forum, so you can see more details about the issue here:

http://forums.iis.net/t/1150788.aspx

At this point, it seems like there are two issues:

1 - The Response.Cookies collection available to managed code is not populated with cookies set by a native handler

2 - The Response.Headers collection available to managed code seems to overwrite collection items when there are duplicate response headers (instead of concatenating them with a semi-colon).

Any help you can provide me would be greatly appreciated.

Thanks,

Cooper

Re: IIS7 Response.Cookies Collection is Empty

ksingla — Fri, 01 Aug 2008 05:37:52 GMT

Hi CooperNYC,

Can you pls check if Set-Cookie header is seen correctly in managed module in the later stages of the pipeline? It is possible that Set-Cookie header is not parsed to fill the cookies collection everytime transition from native to managed module happens. I can followup with Asp.Net team to find if this is unexpected behavior.

Thanks,
Kj

IIS7 Response.Cookies Collection is Empty

CooperNYC — Wed, 30 Jul 2008 11:56:32 GMT

On IIS7, the HttpContext.Current.Response.Cookies collection seems to only contain cookies that ASP.NET creates. So on requests where a Classic ASP page sets 3 cookies, the collection when accessed via an HttpModule (later in the pipeline) is empty. This seems like a bug, right?