[thelist] IIS equivalent of Apache "Permanent redirect" directive?

[Morgan Kelsey]

bob,

>
> I would think handling it all via <CFLOCATION> would be more SE
> friendly.
>

if the URL is going to change, i believe most spiders prefer it happen on
the client side, but it's possible that it doesn't matter these days....
here's an interesting thread i just found on it:
http://www.sitepointforums.com/showthread.php?s=&threadid=75386

It's definitely something you'll find to be inconsistent from search engine
to search engine. some will care, others won't. If you do use cflocation, i
would pass a 302 with <cfheader ...> like that thread suggests.

In a custom 404 situation, the URL doesn't change when the error handler is
invoked in URL mode (and a 404 isn't actually sent to the client either). so
the usual method is to include the page that should have occured, which
requires no further redirection on either side (really the best solution).


hth,

nagrom