ISAPI_Rewrite (http://www.isapirewrite.com)
ISAPI_Rewrite allows IIS Web Servers to utilize .htaccess files much like Apache web servers.


Example .htaccess file:
# Helicon ISAPI_Rewrite configuration file
# Version

RewriteEngine On

#RewriteCond %{HTTP_HOST} ^yourDomain.com$ [NC] #RewriteLogLevel 9

RewriteRule company.php http://yourDomain.com/new [R=301,L] ———


301 Redirects
Redirect from one internal page to another, or an entirely new URL

Redirect 301 /oldpage.html http://www.yoursite.com/newpage.html
Redirect 301 /oldpage2.html http://www.yoursite.com/folder/

Redirect entire site:

Redirect 301 / http://www.new-site.com/

Aliased domain incoming – redirect to sub page

RewriteCond %{HTTP_HOST} ^aliasedDomain.com [NC] RewriteRule ^(.*)$ http://hostedDomain.com/?page_id=7338 [R=301,NC]



Need to have domain.com/portal ignore the other .htaccess rewrite rules
Try adding
to your ruleset before the other rewrite rules but after
RewriteEngine on



Full documentation here: http://httpd.apache.org/docs/current/mod/mod_rewrite.html
Useful guide to mod_rewrite here: http://httpd.apache.org/docs/2.0/misc/rewriteguide.html
Helpful Tips: http://www.askapache.com/htaccess/modrewrite-tips-tricks.html


Helicon APE
# Helicon Ape version
# HN MUA-603-76565

RewriteEngine on

# Redirect 301 /about/mission http://domain.com/about-us/ — First rule so that it actually works.
RewriteRule ^about/mission.? /about-us/ [R=301,L]

# BEGIN WordPress

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . index.php [L]

#Seems this https request rewrite isnt working properly, nor was present before in the IIS rewrite rule- now disabled since helicon ape is enabled.

#RewriteRule .? http(?%1s)://www.%2%3 [R=301,L]#
#RewriteCond %{HTTPS} (on)?
#RewriteCond %{HTTP:Host} ^(?!www.)(.+)$ [NC] #RewriteCond %{REQUEST_URI} (.+)

# END WordPress