-
Posted to
IIS7 - Known Issues and Workarounds
by
CooperNYC
on
08-04-2008, 3:46 PM
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, ...
-
Posted to
IIS7 - Known Issues and Workarounds
by
CooperNYC
on
08-01-2008, 10:15 AM
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 ...
-
Posted to
IIS7 - Classic ASP
by
CooperNYC
on
07-31-2008, 4:29 PM
Carlos, thanks for looking into this. Unfortunately, your test did not factor in that each Set-Cookie header has a semicolon in it. So your ASP code above produces the following:
Set-Cookie: foo=bar; path=/
Set-Cookie: foo2=bar2; path=/
So when I re-produced your test above, I get the following:Response.Cookies.Count: ...
-
Posted to
IIS7 - Classic ASP
by
CooperNYC
on
07-30-2008, 11:46 PM
Nope, Response.Headers["Set-Cookie"] only shows the LAST one from the response. It's almost like IIS7 is overwriting the Response.Headers entries when there are duplicate headers instead of appending them.
I also ran a test where I tried to read the "X-Powered-By" headers on a response with two of them and ...
-
Posted to
IIS7 - Classic ASP
by
CooperNYC
on
07-30-2008, 6:33 PM
I have an HttpModule on IIS7 that needs to read all cookies set by my Classic ASP application. It seems like the HttpModule can only see the cookies set by ASP.NET applications and not Classic ASP (using HttpResponse.Cookies). I also tried using HttpResponse.Headers, but this is limited to only seeing ONE cookie (if multiple are set on ...
-
Posted to
IIS7 - Known Issues and Workarounds
by
CooperNYC
on
07-30-2008, 7:56 AM
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?
-
Posted to
IIS7 - Extensibility
by
CooperNYC
on
07-21-2008, 2:57 PM
I am trying to write an HttpModule to log all outbound Set-Cookie headers for any response generated by IIS7 (including un-managed handlers like ASP and PHP). My code works fine with managed requests, but for un-managed requests the Response.Cookies collection is always empty (HttpContext.Current.Response.Cookies.Count=0). I have tried ...