Comments on: Response.Redirect and Output Caching Trouble http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools. Mon, 26 Jul 2010 02:01:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: admin http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html/comment-page-1#comment-1681 admin Fri, 15 Jan 2010 01:18:50 +0000 http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html#comment-1681 Ta Duc, I don't know of a way to cache the redirect. Caching usually applies to the content, not the headers. It wouldn't save you much anyway since the server has to process the headers anyway. Ta Duc, I don’t know of a way to cache the redirect. Caching usually applies to the content, not the headers. It wouldn’t save you much anyway since the server has to process the headers anyway.

]]> By: Ta Duc http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html/comment-page-1#comment-1680 Ta Duc Thu, 14 Jan 2010 02:37:50 +0000 http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html#comment-1680 Is there any that can actually cache the output result of a redirect page? for instance, i have a page that query something first and then redirect user to that result. Is there anyway to apply cache to this? I tried output cache on the action, but when check it up in Linq2sql profiler, i got queries everytime without caching... Thanks, BTW, can you add the function to automatic send an email if there is respond to this? If not i will be having a lot of hardtime tracing back your page. or you could reply to my email: duc at ducdigital dot com... Thanks Is there any that can actually cache the output result of a redirect page? for instance, i have a page that query something first and then redirect user to that result. Is there anyway to apply cache to this?

I tried output cache on the action, but when check it up in Linq2sql profiler, i got queries everytime without caching…

Thanks,

BTW, can you add the function to automatic send an email if there is respond to this? If not i will be having a lot of hardtime tracing back your page. or you could reply to my email: duc at ducdigital dot com… Thanks

]]> By: Rem http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html/comment-page-1#comment-731 Rem Mon, 13 Oct 2008 18:14:18 +0000 http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html#comment-731 Nice post... Nice post…

]]> By: superjason http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html/comment-page-1#comment-730 superjason Mon, 13 Oct 2008 15:52:43 +0000 http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html#comment-730 Shawn, that will fix the issue. However, there are dozens of mobile device user agents (even more on the desktop). This has 2 effects: 1. Excessive memory is used (not sure how substantial) 2. More importantly, you're losing the likelihood of hitting the cache. You want users to hit the cache for the benefit of the server, AND for a quick response on their end. You could certainly focus on varying by browser and version to help out a little bit. It goes without saying that you'll have to determine which method is going to work for your project. Shawn, that will fix the issue. However, there are dozens of mobile device user agents (even more on the desktop).

This has 2 effects:
1. Excessive memory is used (not sure how substantial)
2. More importantly, you’re losing the likelihood of hitting the cache. You want users to hit the cache for the benefit of the server, AND for a quick response on their end.

You could certainly focus on varying by browser and version to help out a little bit.

It goes without saying that you’ll have to determine which method is going to work for your project.

]]> By: Obishawn http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html/comment-page-1#comment-729 Obishawn Mon, 13 Oct 2008 15:42:44 +0000 http://www.ytechie.com/2008/10/responseredirect-and-output-caching-trouble.html#comment-729 For the mobile browser example, couldn't you also use < %@ OutputCache Duration="120" VaryByParam="*" VaryByHeader="User-Agent" %>. Then all browsers with the same user agent would have the same behavior be it a redirect or a cached page being rendered? Personally I think you should always be varying a page by the user agent because certain third party (and I think even .NET Framework) controls render differently depending on the browser you are using. For the mobile browser example, couldn’t you also use < %@ OutputCache Duration="120" VaryByParam="*" VaryByHeader="User-Agent" %>. Then all browsers with the same user agent would have the same behavior be it a redirect or a cached page being rendered?

Personally I think you should always be varying a page by the user agent because certain third party (and I think even .NET Framework) controls render differently depending on the browser you are using.

]]>