Our web.config file has 1300 redirects in it and growing all the time. Its a mixture of 4 site rebuilds over 15 years and marketing vanity URLS. My question is 3 part.

  1. does having to search through 1300 redirects every time a vanity url is used impact performance in any meaningful way. Im sure it does, but is that so many its slowing things down.

  2. How can i track over time which ones are actually being used. Im sure some that are over 10 years old probably never get used. i reckon i could cut the number down by 60% as they never get used anymore.

  3. Is it worth doing?

Thanks for any help!

  • are you using native IIS Redirects, or URL Rewrite? – Peter Hahndorf Mar 15 '18 at 4:24
  • Last time I came in contact with IIS (what's in a name, eh?) it had access logs almost like Apache. Shouldn't be hard to extract some statistics from those. Put the most requested first in your redirect list. – Gerard H. Pille Mar 15 '18 at 7:38
  • Thanks for taking the time to comment. Im not sure the difference. Im doing it like this : 'code' <add wildcard="/ed" destination="teachingcareers.englishfirst.com/graduate-jobs-in-china-package/…> – PJSANTA Mar 16 '18 at 1:32
  • Use Log Parser to go over the 301 responses in IIS log files. That might help you know which rules are still in use. – Lex Li Apr 16 '18 at 19:52

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.