OpUrl - Powerful URL re-writing for IIS Configuration Once OpUrl is installed, it's configured using a single file. The OpUrl.txt file can be found in the system directory (usually C:\Winnt\system32) contains a list of all the domains for which re-writing should occur. It's a simple text file in the following format: # comment [www.domain.com] /products/([0-9]+) /product.asp\?id=$1 Currently there can only be one domain listed for each set of re-writing rules. Therefore, if your site is accessed using different host header names, you will need to duplicate the rules for each one: # www.domain.com, support.domain.com and 1.2.3.4 all # reference the same site [www.domain.com] /products/([0-9]+) /product.asp\?id=$1 [support.domain.com] /products/([0-9]+) /product.asp\?id=$1 [1.2.3.4] /products/([0-9]+) /product.asp\?id=$1 Better configuration support for multiple aliases will be added in the next version. When you make a change to the configuration file, it will not be picked up until OpUrl is reloaded. This normally involves restarting IIS (using admin script IISRESET if using Windows 2000). Because of this, it is best to develop and test your rules on a development server, before deploying to production. As the file is parsed, information will be written to file OpUrl.log. Always check the contents of this file after changing your configuration. Examples The regular expression support in OpUrl is very powerful. It can be put to many uses, here are a couple of examples: Encourage search engines to index your site by using static URLs instead of dynamic Hide the construction of your site from competitors or hackers Provide easily readable and more memorable links for your users

About OpURL Download Installation Configuration Purchase   New! Forums