Sunday, June 9, 2013

Google Chrome and the 301 Redirect Cache or Why are my 301 Redirects not hitting my server

301 Redirects are important to maintain search rankings and help users with browser bookmarks still find the right location on your site.
This article helps you build your own 301 redirect handler for Sitecore: Create the ultimate 301 Redirect Handler for Sitecore

PROBLEM: Recently while building it myself I found an interesting but/feature of chrome.  When I was debugging my 301 redirect handler the first time I hit the URL it hit my breakpoint and I could debug the update however when I hit it again it redirected without hitting my handler. It turns out this is a feature of chrome.  Since the 301 is a permanent redirect, Chrome remembers the redirect and caches it.
Here is an article that explains it more: Google Chrome Caches 301 Redirects

SOLUTION: There are actually two possible solutions:
  1. Debug in Internet Explorer and FireFox and once working use Chrome once to ensure it redirects.
  2. Chrome has a way of turning this feature off How Can I Make Chrome Stop Caching Redirects
Hope it helps someone else in the Guild avoid the same issue.

If you have a tip, trick or resource you would like to share with the guild please email me at

No comments:

Post a Comment