Search results matching tag 'Rules Import'

Re: Images / CSS / files not visible/reachable

ruslany — Mon, 23 Feb 2009 18:20:59 GMT

The regular expression that you have in "Imported Rule 1" is too broad, i.e. it always matches. This causes two things: 1. None of the subsequent rules are ever executed. 2. It rewrites the requests for css and image files to index.php.

To fix that you can do the following:

1. Add the following conditions to the "Imported Rule 1":

This will cause to rule to not execute for css and image files.

2. Move the "Imported Rule 1" to the end of the rules list.

Re: Rewrite URI

ruslany — Wed, 03 Dec 2008 16:17:29 GMT

Option for importing of mod_rewrite rules available only when you open URL rewriter UI on a site of vdir level. It is not available on a server level.

Rule import Wizard issues

species5618 — Thu, 26 Jun 2008 10:13:09 GMT

Just looking at the URL-Rewrite module with a plan to POC wordpress MU and came accross a few things

1st
being the rule import does not like "RewriteBase BASE/" saying it is not supported,
Great, but it woudl be nice I could then manualy edit the generated XML rule set, so I can apply them, instead of having to Edit the source .htaccess and re-import the file

2nd
Involve the "[L]" last rule option on .htaccess
the import wizard XML preview correctly included the 'stopProcessing="true" ' setting, but having applied the rules, the ' stopProcessing="true" ' did not get applied to the imported rules

RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
Became
    <rule name="ImportedRule5" >
      <match url="^([_0-9a-zA-Z-]+/)?(wp-.*)" ignoreCase="false" />
      <action type="Rewrite" url="{R:2}" />
    </rule>
NOT
    <rule name="ImportedRule5" stopProcessing="true">
      <match url="^([_0-9a-zA-Z-]+/)?(wp-.*)" ignoreCase="false" />
      <action type="Rewrite" url="{R:2}" />
    </rule>

Re: L flag not being imported from mod_rewrite

ruslany — Thu, 12 Jun 2008 00:19:07 GMT

Looks like this is a bug in the rule import tool. Thanks for reporting this - good catch!

Re: QSA being applied by default when importing from mod_rewrite

ruslany — Thu, 12 Jun 2008 00:00:17 GMT

The reason why the appendQueryString is set to true is because its semantics in IIS is somewhat different from QSA in mod_rewrite.

In mod_rewrite if substitution string does not contain query string then the original query string is preserved regardless of QSA flag. For example this rewrite rule:

rewriterule a b

will replace "a?c=1" to "b?c=1".

In IIS URL rewriter if appendQueryString is set to false then it means that original query string will never be preserved. For example this rewrite rule:

will replace "a?c=1" to "b". Notice that the original query string will be dropped.

So in order to get the exact same behavior of the converted mod_rewrite rule in IIS the rule importer tool sets this flag to true if the substitution url in mod_rewrite rule did not have the query string.

Re: L flag not being imported from mod_rewrite

ruslany — Wed, 11 Jun 2008 23:37:17 GMT

The "L" flag stands for "Last rule", meaning that if this rule was evaluated successfully then no subsequent rules will be evaluated. In URL rewrite module we have a rule attribute called "stopProcessing", which has the same semantics as L flag in mod_rewrite. The rule converter should set this flag to true when converting any mod_rewrite rules that use "L" flag. If that is not the case for you - could you post your rule here?

Also, the rule import tool understands only mod_rewrite syntax. ISAPI_Rewrite syntax, while similar to mod_rewrite, has some unique flags and attributes, so the tool will not be convert ISAPI_Rewrite rules reliably.