IIS Server Load for 500 Page Level 301 Redirects
-
We are migrating content from 10 sub domains to our www site. On an IIS sever, what is potential server load impact, if any, for setting up 500 plus page level redirects?
-
Very minimal. A 301 redirect is delivered via an HTTP status code which is the first thing to get crawled on a page. there won't be any other server load other than sending it along it's way to it's new location.
Edit: To put this in other words, it's not going to be any worse than your IIS server having to deliver an additional 500 plus HTTP status code 200.
-
Thanks for the HTTP status code analogy. The comment adds the perspective I need to explain this to my technical manager.