Are there any errors for rewriting ColdFusion site url with ISAPI_Rewrite v2?
I was asked to help with ColdFusion development and one of the tasks would be to rewrite the urls, mainly turning url parameters into a cleaner url.
The site is on a cf8 hosting service powered by iis with Helicon Tech ISAPI_Rewrite v2.
Are there any things I should pay attention to?
Thanks.
a source to share
It should be good. IIS (or the addition of ISAPI) deals with rewriting the url and then passes it to the CF as if it were requested as the original url.
Most people rewrite URLs to improve their SERP rankings. The key to this is that the original url that was previously set returns a 301 (permanently redirected) redirect to your new url. This keeps the "link juice" associated with the old URL. Don't use CFLOCATION for redirection - this tag does 302 ...
a source to share
I have been using ISAPI_Rewrite and ColdFusion for several years and have had good results.
I would recommend upgrading to version 3 if possible. Although version 2 worked fine, I found the latest version easier to use as it is compatible with mod_rewrite .
a source to share
The bottom line is that the Rewriter URL and your application server (ColdFusion or others) should never work together. If they are, you probably configured your rewrite rules incorrectly (or are using a broken rewriter).
The Rewriter URL changes the appearance of the request before it is sent to the application server. While the end result is foo.cfm? Var = value, be it the actual url or the rewrite result, that will be fine.
a source to share