« Previous Next »

• 02-09-2009, 1:47 AM

  In reply to

  anilr Joined on 05-23-2006, 10:13 PM Redmond, WA Posts 2,343	Re: Session problem with IIS7 Reply Contact You should not be enabling output caching for any response which depends on session state - I am not sure what the IIS bug here is. Anil Ruia Senior Software Design Engineer IIS Core Server

• 02-09-2009, 6:43 AM

  In reply to

  ingigauti Joined on 01-15-2009, 10:26 AM Posts 11

  Re: Session problem with IIS7 Reply Contact How can anybody know that? IIS actually uses .aspx and .axd as an example, and I bet that 95% of all dynamic pages uses session. There should be a fat warning sign in the "Add Cache Rule" window and IIS should detect if session is enable on the page. Where is it mentioned that session should be disabled on these pages? http://technet.microsoft.com/en-us/library/cc732475.aspx I'm still saying this is a bug in IIS and a major one. Sorry, I can't agree with you that this is by design when there is no mention about it Microsoft own documents. Even when pressing F1 when you are in the "Add Cache Rule" window in IIS, the help document comes up and there is nothing about not caching session pages.

• 07-01-2010, 4:22 PM

  In reply to

  ken.fleming@smartdrive.net Joined on 01-29-2008, 5:15 PM Posts 1

  Re: Session problem with IIS7 Reply Contact We have the same problem.  We turned of caching for aspx for both user and kernel and we thought we were safe, but we just had it happend again Questions:  Can MVC effect this since it does not make a request to aspx                      We do have caching still enabled on public portal (marketing site) from which the customer can log into the back end which is a secure site which has caching disabled.  Can this be the cause?

• 07-02-2010, 6:07 AM

  In reply to

  ingigauti Joined on 01-15-2009, 10:26 AM Posts 11

  Re: Session problem with IIS7 Reply Contact The problem is that you have the caching still enabled on the public portal, you can't have the caching enabled on any static or dynamic files that are served from the same domain. If you want to cache the static files the solution is to to setup a subdomain for your domain, something like static.yourdomain.com and serve all static content from that domain. The default session id doesn't transfer between subdomain so you are safe. This so called output caching in IIS7 is kinda f**ked up and useless.