blocks|key|210130|text|问题中所示的IIS入站规则可以正常工作。我必须清除浏览器缓存，并在index.html页面的<head>部分的顶部添加以下行：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|210131|<base+href="/myApplication/app/"+/>|code-block|syntax|javascript|210132|这是因为我在本地主机中有多个应用程序，因此对其他部分的请求被发送到localhost/app/view1而不是localhost/myApplication/app/view1|210133|希望这对某些人有帮助！|210134|entityMap^0|1A|6|0|0|X|J|1J|X|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

The IIS inbound rules as shown in the question DO work. I had to clear the browser cache and add the following line in the top of my <code>&lt;head&gt;</code> section of the index.html page:

<pre><code>&lt;base href="/myApplication/app/" /&gt;
</code></pre>

This is because I have more than one application in localhost and so requests to other partials were being taken to <code>localhost/app/view1</code> instead of <code>localhost/myApplication/app/view1</code>

Hopefully this helps someone!

blocks|key|3068523|text|在我的例子中，在我设置了正确的重写规则后，我一直得到403.14分。原来我有一个与我的一个URL路由同名的目录。一旦我删除了IsDirectory重写规则，我的路由就能正常工作。是否存在删除目录否定可能会导致问题的情况？我想不出像我这样的人。我能想到的唯一情况是，如果你能用你的应用程序浏览一个目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3068524|<rule+name="fixhtml5mode"+stopProcessing="true">
++<match+url=".*"/>
++<conditions+logicalGrouping="MatchAll">
++++<add+input="{REQUEST_FILENAME}"+matchType="IsFile"+negate="true"+/>
++</conditions>
++<action+type="Rewrite"+url="/"+/>
</rule>|code-block|syntax|javascript|3068525|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In my case I kept getting a 403.14 after I had setup the correct rewrite rules. It turns out that I had a directory that was the same name as one of my URL routes. Once I removed the IsDirectory rewrite rule my routes worked correctly. Is there a case where removing the directory negation may cause problems? I can't think of any in my case. The only case I can think of is if you can browse a directory with your app.

<pre><code>&lt;rule name="fixhtml5mode" stopProcessing="true"&gt;
 &lt;match url=".*"/&gt;
 &lt;conditions logicalGrouping="MatchAll"&gt;
 &lt;add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /&gt;
 &lt;/conditions&gt;
 &lt;action type="Rewrite" url="/" /&gt;
&lt;/rule&gt;
</code></pre>

blocks|key|210168|text|在web.config中设置了$locationProvider.html5Mode(true)之后，我在app.js中写出了一条规则。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|210169|希望，帮助某人摆脱困境。|210170|++<system.webServer>
++++<rewrite>
++++++<rules>
++++++++<rule+name="AngularJS+Routes"+stopProcessing="true">
++++++++++<match+url=".*"+/>
++++++++++<conditions+logicalGrouping="MatchAll">
++++++++++++<add+input="{REQUEST_FILENAME}"+matchType="IsFile"+negate="true"+/>
++++++++++++<add+input="{REQUEST_FILENAME}"+matchType="IsDirectory"+negate="true"+/>
++++++++++++<add+input="{REQUEST_URI}"+pattern="%5E/(api)"+negate="true"+/>
++++++++++</conditions>
++++++++++<action+type="Rewrite"+url="/"+/>
++++++++</rule>
++++++</rules>
++++</rewrite>
++</system.webServer>|code-block|syntax|javascript|210171|在我的index.html中，我将这个添加到了<head>|210172|<base+href="/">|210173|别忘了在服务器上安装IIS+URL+Rewrite。|210174|此外，如果您使用Web+API和IIS，则由于第三个输入(条件的第三行)，如果您的API为www.yourdomain.com/api，则此方法将起作用。|210175|entityMap|0|LINK|mutability|MUTABLE|url|http://www.iis.net/downloads/microsoft/url-rewrite^0|F|X|1H|6|0|0|0|N|6|0|0|A|F|0|0|19|M|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1C|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|S|3|T|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

I write out a rule in web.config after <code>$locationProvider.html5Mode(true)</code> is set in <code>app.js</code>. 

Hope, helps someone out.

<pre><code> &lt;system.webServer&gt;
 &lt;rewrite&gt;
 &lt;rules&gt;
 &lt;rule name="AngularJS Routes" stopProcessing="true"&gt;
 &lt;match url=".*" /&gt;
 &lt;conditions logicalGrouping="MatchAll"&gt;
 &lt;add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /&gt;
 &lt;add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /&gt;
 &lt;add input="{REQUEST_URI}" pattern="^/(api)" negate="true" /&gt;
 &lt;/conditions&gt;
 &lt;action type="Rewrite" url="/" /&gt;
 &lt;/rule&gt;
 &lt;/rules&gt;
 &lt;/rewrite&gt;
 &lt;/system.webServer&gt;
</code></pre>

In my index.html I added this to <code>&lt;head&gt;</code>

<pre><code>&lt;base href="/"&gt;
</code></pre>

Don't forget to install <a href="http://www.iis.net/downloads/microsoft/url-rewrite" rel="noreferrer">IIS URL Rewrite</a> on server.

Also if you use Web API and IIS, this will work if your API is at <code>www.yourdomain.com/api</code> because of the third input (third line of condition).

blocks|key|2855236|text|只有这两个条件的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2855237|++<add+input="{REQUEST_FILENAME}"+matchType="IsFile"+negate="true"+/>
++<add+input="{REQUEST_FILENAME}"+matchType="IsDirectory"+negate="true"+/>|code-block|syntax|javascript|2855238|它们只能在{REQUEST_FILENAME}+exists+physically+on+disk的时间内工作。这意味着在某些情况下，对命名错误的部分视图的请求将返回根页面，而不是404，这将导致angular被加载两次(在某些情况下，它可能会导致令人讨厌的无限循环)。|offset|length|style|CODE|2855239|因此，建议使用一些安全的“回退”规则来避免这些难以解决的问题：|2855240|++<add+input="{REQUEST_FILENAME}"+pattern="(.*?)\.html$"+negate="true"+/>
++<add+input="{REQUEST_FILENAME}"+pattern="(.*?)\.js$"+negate="true"+/>
++<add+input="{REQUEST_FILENAME}"+pattern="(.*?)\.css$"+negate="true"+/>|2855241|或者是matches+any+file+ending：|2855242|<conditions>
++
++<add+input="{REQUEST_FILENAME}"+pattern=".*\.[\d\w]%2B$"+negate="true"+/>
</conditions>|2855243|entityMap|0|LINK|mutability|MUTABLE|url|http://sebnilsson.com/c985a7fd/iis-url-rewrite-rules-skipping-files-types/|1^0|0|0|5|I|O|P|0|0|0|0|3|N|1|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@$I|18|J|19|1|1A]]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@$I|1E|J|1F|1|1G]]|A|$]]|$1|S|3|T|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|11]]]]

The issue with only having these two conditions:

<pre><code> &lt;add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /&gt;
 &lt;add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /&gt;
</code></pre>

is that they work only as long as the <code>{REQUEST_FILENAME}</code> <a href="http://sebnilsson.com/c985a7fd/iis-url-rewrite-rules-skipping-files-types/" rel="noreferrer">exists physically on disk</a>. This means that there can be scenarios where a request for an incorrectly named partial view would return the root page instead of a 404 which would cause angular to be loaded twice (and in certain scenarios it can cause a nasty infinite loop).

Thus, some safe "fallback" rules would be recommended to avoid these hard to troubleshoot issues:

<pre><code> &lt;add input="{REQUEST_FILENAME}" pattern="(.*?)\.html$" negate="true" /&gt;
 &lt;add input="{REQUEST_FILENAME}" pattern="(.*?)\.js$" negate="true" /&gt;
 &lt;add input="{REQUEST_FILENAME}" pattern="(.*?)\.css$" negate="true" /&gt;
</code></pre>

or a condition that <a href="http://sebnilsson.com/c985a7fd/iis-url-rewrite-rules-skipping-files-types/" rel="noreferrer">matches any file ending</a>: 

<pre><code>&lt;conditions&gt;
 &lt;!-- ... --&gt;
 &lt;add input="{REQUEST_FILENAME}" pattern=".*\.[\d\w]+$" negate="true" /&gt;
&lt;/conditions&gt;
</code></pre>

blocks|key|3068638|text|我发现的最简单的方法就是将触发404的请求重定向到客户端。这是通过添加标签来实现的，即使设置了$locationProvider.html5Mode(true)也是如此。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3068639|此技巧适用于在同一网站上有更多Web应用程序并需要URL完整性约束(例如，外部身份验证)的环境。下面是一步一步怎么做|3068640|index.html|3068641|正确设置<base>元素|3068642|<base+href="@(Request.ApplicationPath+%2B+"/")">|code-block|syntax|javascript|3068643|web.config|3068644|首先将404重定向到定制页面，例如"Home/Error“|3068645|<system.web>
++++<customErrors+mode="On">
++++++++<error+statusCode="404"+redirect="~/Home/Error"+/>
++++</customErrors>
</system.web>|3068646|家庭控制器|3068647|实现一个简单的ActionResult来“翻译”客户端路由中的输入。|3068648|public+ActionResult+Error(string+aspxerrorpath)+{
++++return+this.Redirect("~/#/"+%2B+aspxerrorpath);
}|3068649|这是最简单的方法。|3068650|3068651|这是可能的(可取吗？)为了利用一些改进的逻辑来增强错误功能，以便仅当url有效时才将404重定向到客户端，并且当在客户端上什么都没有发现时让404正常触发。假设你有这些角度的路线|3068652|.when("/",+{
++++templateUrl:+"Base/Home",
++++controller:+"controllerHome"
})
.when("/New",+{
++++templateUrl:+"Base/New",
++++controller:+"controllerNew"
})
.when("/Show/:title",+{
++++templateUrl:+"Base/Show",
++++controller:+"controllerShow"
})|3068653|只有当URL以"/New“或"/Show/”开头时，才有必要将其重定向到客户端。|3068654|public+ActionResult+Error(string+aspxerrorpath)+{
++++//+get+clientside+route+path
++++string+clientPath+=+aspxerrorpath.Substring(Request.ApplicationPath.Length);

++++//+create+a+set+of+valid+clientside+path
++++string[]+validPaths+=+{+"/New",+"/Show/"+};

++++//+check+if+clientPath+is+valid+and+redirect+properly
++++foreach+(string+validPath+in+validPaths)+{
++++++++if+(clientPath.StartsWith(validPath))+{
++++++++++++return+this.Redirect("~/#/"+%2B+clientPath);
++++++++}
++++}

++++return+new+HttpNotFoundResult();
}|3068655|这只是一个改进逻辑的例子，当然每个web应用程序都有不同的需求|3068656|entityMap^0|1B|X|0|0|0|4|6|0|0|0|0|0|0|7|C|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1K|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|L|3|M|5|N|7|1P|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1R|8|@]|D|@]|E|$]]|$1|U|3|V|5|N|7|1S|8|@]|D|@]|E|$O|P]]|$1|W|3|X|5|6|7|1T|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1U|8|@$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|10|3|11|5|N|7|1X|8|@]|D|@]|E|$O|P]]|$1|12|3|13|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|20|8|@]|D|@]|E|$]]|$1|17|3|18|5|N|7|21|8|@]|D|@]|E|$O|P]]|$1|19|3|1A|5|6|7|22|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|N|7|23|8|@]|D|@]|E|$O|P]]|$1|1D|3|1E|5|6|7|24|8|@]|D|@]|E|$]]|$1|1F|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|1G|$]]

The easiest way I found is just to redirect the requests that trigger 404 to the client. This is done by adding an hashtag even when <code>$locationProvider.html5Mode(true)</code> is set.

This trick works for environments with more Web Application on the same Web Site and requiring URL integrity constraints (E.G. external authentication). Here is step by step how to do

<h3>index.html</h3>

Set the <code>&lt;base&gt;</code> element properly

<pre><code>&lt;base href="@(Request.ApplicationPath + "/")"&gt;
</code></pre>

<h3>web.config</h3>

First redirect 404 to a custom page, for example "Home/Error"

<pre><code>&lt;system.web&gt;
 &lt;customErrors mode="On"&gt;
 &lt;error statusCode="404" redirect="~/Home/Error" /&gt;
 &lt;/customErrors&gt;
&lt;/system.web&gt;
</code></pre>

<h3>Home controller</h3>

Implement a simple <code>ActionResult</code> to "translate" input in a clientside route.

<pre><code>public ActionResult Error(string aspxerrorpath) {
 return this.Redirect("~/#/" + aspxerrorpath);
}
</code></pre>

This is the simplest way.

<hr>

It is possible (advisable?) to enhance the Error function with some improved logic to redirect 404 to client only when url is valid and let the 404 trigger normally when nothing will be found on client.
Let's say you have these angular routes

<pre><code>.when("/", {
 templateUrl: "Base/Home",
 controller: "controllerHome"
})
.when("/New", {
 templateUrl: "Base/New",
 controller: "controllerNew"
})
.when("/Show/:title", {
 templateUrl: "Base/Show",
 controller: "controllerShow"
})
</code></pre>

It makes sense to redirect URL to client only when it start with "/New" or "/Show/"

<pre><code>public ActionResult Error(string aspxerrorpath) {
 // get clientside route path
 string clientPath = aspxerrorpath.Substring(Request.ApplicationPath.Length);

 // create a set of valid clientside path
 string[] validPaths = { "/New", "/Show/" };

 // check if clientPath is valid and redirect properly
 foreach (string validPath in validPaths) {
 if (clientPath.StartsWith(validPath)) {
 return this.Redirect("~/#/" + clientPath);
 }
 }

 return new HttpNotFoundResult();
}
</code></pre>

This is just an example of improved logic, of course every web application has different needs

blocks|key|2855280|text|我一直在尝试将一个简单的Angular+7应用程序部署到Azure+Web+App。一切工作正常，直到您刷新页面为止。这样做，向我呈现了一个500错误移动的内容。我在Angular文档和一些论坛上都读到过，我需要在已部署的解决方案中添加一个web.config文件，并确保重写规则后退到index.html文件。在经历了数小时的挫折和试错测试后，我发现错误非常简单:在我的文件标记周围添加一个标记。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2855281|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've been trying to deploy a simple Angular 7 application, to an Azure Web App.
Everything worked fine, until the point where you refreshed the page. Doing so, was presenting me with an 500 error - moved content.
I've read both on the Angular docs and in around a good few forums, that I need to add a web.config file to my deployed solution and make sure the rewrite rule fallback to the index.html file.
After hours of frustration and trial and error tests, I've found the error was quite simple: adding a tag around my file markup.

blocks|key|214791|text|我遇到了类似的问题，Angular和IIS在手动刷新时抛出了404状态代码，并尝试了投票最多的解决方案，但这对我不起作用。我还尝试了一堆其他的解决方案，不得不处理WebDAV和更改处理程序，但都没有成功。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|214792|幸运的是，我找到了this+solution，它可以工作(去掉了我不需要的部分)。因此，如果以上方法都不适用于您，甚至在尝试它们之前，请尝试一下，看看这是否能解决您在iis问题上的angular部署。|offset|length|214793|将代码片段添加到站点根目录下的webconfig中。据我所知，它从任何继承(applicationhost.config，machine.config)中删除了404状态代码，然后在站点级别创建了404状态代码，并将主页重定向为自定义的404页面。|214794|<?xml+version="1.0"+encoding="UTF-8"?>
<configuration>
++<system.webServer>
++++<httpErrors+errorMode="Custom">
++++++<remove+statusCode="404"/>
++++++<error+statusCode="404"+path="/index.html"+responseMode="ExecuteURL"/>
++++</httpErrors>
++</system.webServer>
</configuration>|code-block|syntax|javascript|214795|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/angular/angular-cli/issues/11285#issuecomment-415722939^0|0|9|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I had a similar issue with Angular and IIS throwing a 404 status code on manual refresh and tried the most voted solution but that did not work for me. Also tried a bunch of other solutions having to deal with WebDAV and changing handlers and none worked. 

Luckily I found <a href="https://github.com/angular/angular-cli/issues/11285#issuecomment-415722939" rel="nofollow noreferrer">this solution</a> and it worked (took out parts I didn't need). So if none of the above works for you or even before trying them, try this and see if that fixes your angular deployment on iis issue.

Add the snippet to your webconfig in the root directory of your site. From my understanding, it removes the 404 status code from any inheritance (applicationhost.config, machine.config), then creates a 404 status code at the site level and redirects back to the home page as a custom 404 page.

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;configuration&gt;
 &lt;system.webServer&gt;
 &lt;httpErrors errorMode="Custom"&gt;
 &lt;remove statusCode="404"/&gt;
 &lt;error statusCode="404" path="/index.html" responseMode="ExecuteURL"/&gt;
 &lt;/httpErrors&gt;
 &lt;/system.webServer&gt;
&lt;/configuration&gt;
</code></pre>

blocks|key|3068712|text|不幸的是，最好的解决方案不适合我使用.NET+Framework4.5和IIS6.2。我首先按照所有步骤安装微软的URL+Rewrite+tool，然后调整我的Web.config文件，使其包含以下内容，从而使其正常工作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3068713|++++<system.webServer>
++++
++++<rewrite>
++++++<rules>
++++++++<rule+name="Angular+Routes"+stopProcessing="true">
++++++++++<match+url="(%5E(?!.*\.[\d\w]%2B$).*)"+/>
++++++++++<conditions+logicalGrouping="MatchAny">
++++++++++++<add+input="{REQUEST_URI}"+pattern=".*\/api\/.*"+negate="true"+/>
++++++++++</conditions>
++++++++++<action+type="Rewrite"+url="./index.html"+/>
++++++++</rule>
++++++</rules>
++++</rewrite>
++</system.webServer>|code-block|syntax|javascript|3068714|第一个正则表达式使用负的查找头来不匹配URI末尾的任何文件扩展名。然后，在条件中，包括/api/在内的任何URI也将被忽略。|3068715|这种配置允许我在不中断路由的情况下刷新Angular应用程序，也可以在不重写的情况下访问我的API。|3068716|entityMap|0|LINK|mutability|MUTABLE|url|https://www.iis.net/downloads/microsoft/url-rewrite^0|28|A|1L|G|0|0|0|17|5|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|16|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

The top solution for this unfortunately did not work for me using .NET framework 4.5 and IIS 6.2. I got it to work by first following all the steps to install the <a href="https://www.iis.net/downloads/microsoft/url-rewrite" rel="nofollow noreferrer">URL Rewrite tool</a> from Microsoft, then adjusting my <code>Web.config</code> file to include the following:
<pre><code> &lt;system.webServer&gt;
 &lt;!-- handlers etc --&gt;
 &lt;rewrite&gt;
 &lt;rules&gt;
 &lt;rule name=&quot;Angular Routes&quot; stopProcessing=&quot;true&quot;&gt;
 &lt;match url=&quot;(^(?!.*\.[\d\w]+$).*)&quot; /&gt;
 &lt;conditions logicalGrouping=&quot;MatchAny&quot;&gt;
 &lt;add input=&quot;{REQUEST_URI}&quot; pattern=&quot;.*\/api\/.*&quot; negate=&quot;true&quot; /&gt;
 &lt;/conditions&gt;
 &lt;action type=&quot;Rewrite&quot; url=&quot;./index.html&quot; /&gt;
 &lt;/rule&gt;
 &lt;/rules&gt;
 &lt;/rewrite&gt;
 &lt;/system.webServer&gt;
</code></pre>
The first regular expression uses negative look-aheads to NOT match any file extension at the end of the URI. Then, inside the condition, any URI including <code>/api/</code> is also ignored.
This configuration allows me to refresh the Angular app without breaking the routing and also access my API without being re-written.

I have the <a href="https://github.com/angular/angular-seed" rel="noreferrer">AngularJS seed project</a> and I've added 

<pre><code>$locationProvider.html5Mode(true).hashPrefix('!');
</code></pre>

to the app.js file. I want to configure IIS 7 to route all requests to 

<pre><code>http://localhost/app/index.html
</code></pre>

so that this works for me. How do I do this?

Update:

I've just discovered, downloaded and installed the <a href="http://www.iis.net/downloads/microsoft/url-rewrite" rel="noreferrer">IIS URL Rewrite module</a>, hoping this will make it easy and obvious to achieve my goal.

Update 2:

I guess this sums up what I'm trying to achieve (taken from the <a href="http://docs.angularjs.org/guide/dev_guide.services.$location" rel="noreferrer">AngularJS Developer documentation</a>):

<blockquote>
 Using this mode requires URL rewriting on server side,
 basically you have to rewrite all your links to entry point of your
 application (e.g. index.html)
</blockquote>

Update 3:

I'm still working on this and I realise I need to NOT redirect (have rules that rewrite) certain URLs such as 

<pre><code>http://localhost/app/lib/angular/angular.js
http://localhost/app/partials/partial1.html
</code></pre>

so anything that is in the css, js, lib or partials directories isn't redirected. Everything else will need to be redirected to app/index.html

Anyone know how to achieve this easily without having to add a rule for every single file?

Update 4:

I have 2 inbound rules defined in the IIS URL Rewrite module. The first rule is:

<img src="https://i.stack.imgur.com/3vFmW.png" alt="IIS URL Rewrite Inbound Rule 1">

The second rule is:

<img src="https://i.stack.imgur.com/e9zKY.png" alt="IIS URL Rewrite Inbound Rule 2">

Now when I navigate to localhost/app/view1 it loads the page, however the supporting files (the ones in the css, js, lib and partials directories) are also being rewritten to the app/index.html page - so everything is coming back as the index.html page no matter what URL is used. I guess this means my first rule, that is supposed to prevent these URLs from being processed by the second rule, isn't working.. any ideas? ...anyone? ...I feel so alone... :-(

How do I configure IIS for URL Rewriting an AngularJS application in HTML5 mode?

身份验证

服务器

Web App

路由

我有，并且我添加了$locationProvider.html5Mode(true).hashPrefix('!');添加到app.js文件。我想将IIS 7配置为将所有请求路由到http://localhost/app/index.html所以这对我来说是有效的。我该怎么做呢？更新：我刚刚发现、下载并安装了，希望这能...

问如何配置IIS以便在HTML5模式下重写AngularJS应用程序？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置IIS以便在HTML5模式下重写AngularJS应用程序？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置IIS以便在HTML5模式下重写AngularJS应用程序？
EN