blocks|key|1283215|text|该选项只需在firebase.json文件中设置一个标志，将所有URL重定向到/index.html。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1283216|"rewrites":+[+{
++"source":+"**",
++"destination":+"/index.html"
}+]|code-block|syntax|javascript|1283217|有关更多信息，请参见Firebase托管文档，其中还包含了这个更完整的示例：|1283218|“宿主”：{+//+./在“宿主”“重写”中添加“重写”属性：{/+index.html，用于处理对不存在“源”："**“、”目的地“："/index.html”}的文件或目录的请求。{+//+index.html用于请求"/foo“和"/foo/**”//使用"/foo/**“只匹配"/foo/xyz”之类的路径，但不匹配"/foo“源："/foo{，/**}"，”目的“："/index.html”}，{/排除指定路径重写“/foo”：“/@(Js)/**”，“目的地”："/index.html“}|blockquote|1283219|entityMap|0|LINK|mutability|MUTABLE|url|https://firebase.google.com/docs/hosting/full-config#rewrites^0|6|D|13|B|0|0|A|C|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|M|3|N|5|O|7|17|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

That option simply sets a flag in the <code>firebase.json</code> file to redirect all URLs to <code>/index.html</code>.
<pre><code>&quot;rewrites&quot;: [ {
 &quot;source&quot;: &quot;**&quot;,
 &quot;destination&quot;: &quot;/index.html&quot;
} ]
</code></pre>
See the <a href="https://firebase.google.com/docs/hosting/full-config#rewrites" rel="noreferrer">documentation of Firebase Hosting</a> for more information, which also contains this fuller example:
<blockquote>
<pre><code>&quot;hosting&quot;: {
 // ...

 // Add the &quot;rewrites&quot; attribute within &quot;hosting&quot;
 &quot;rewrites&quot;: [ {
 // Serves index.html for requests to files or directories that do not exist
 &quot;source&quot;: &quot;**&quot;,
 &quot;destination&quot;: &quot;/index.html&quot;
 }, {
 // Serves index.html for requests to both &quot;/foo&quot; and &quot;/foo/**&quot;
 // Using &quot;/foo/**&quot; only matches paths like &quot;/foo/xyz&quot;, but not &quot;/foo&quot;
 &quot;source&quot;: &quot;/foo{,/**}&quot;,
 &quot;destination&quot;: &quot;/index.html&quot;
 }, {
 // Excludes specified pathways from rewrites
 &quot;source&quot;: &quot;!/@(js|css)/**&quot;,
 &quot;destination&quot;: &quot;/index.html&quot;
 } ]
}
</code></pre>
</blockquote>

blocks|key|1046747|text|完整的例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1046748|{
++"hosting":+{
++++"public":+".",
++++"rewrites":+[
++++++{
++++++++"source":+"**",
++++++++"destination":+"/index.html"
++++++}
++++]
++}
}|code-block|syntax|javascript|1046749|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|$]]

Full example:

<pre><code>{
 "hosting": {
 "public": ".",
 "rewrites": [
 {
 "source": "**",
 "destination": "/index.html"
 }
 ]
 }
}
</code></pre>

blocks|key|2037045|text|官方Firebase解释：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2037046|我们去年使用了这个选项(Q1+&+Q2)，但它似乎什么也没做，但是现在当我们应用它时，事情肯定是完全不同的。关于它所做的一切的完整的官方解释如下：|2037047|https://firebase.google.com/docs/hosting/url-redirects-rewrites#section-rewrites|offset|length|2037048|在同一页的下一节中，甚至还有一些关于标题使用的有用信息。|2037049|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|28|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

<h2>Official Firebase explanation:</h2>

We had used that option last year (Q1 &amp; Q2) but it seemed to do nothing, but nowadays when we apply it, definitely things work very different.
The complete official explanation of what it does comes in here:

<a href="https://firebase.google.com/docs/hosting/url-redirects-rewrites#section-rewrites" rel="nofollow noreferrer">https://firebase.google.com/docs/hosting/url-redirects-rewrites#section-rewrites</a>

There's even some useful information about Headers usage in the next section of the same page.

blocks|key|1283275|text|注意:如果您希望服务器端呈现，键入No并按以下方式设置rewrites：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1283276|"rewrites":+[
++{
++++"function":+"angularUniversalFunction",
++++"source":+"**"
++}
]|code-block|syntax|javascript|1283277|毕竟，无论您选择什么，都可以在firebase.json文件中更改它。|1283278|entityMap^0|H|2|R|8|0|0|F|D|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|U|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|V|8|@$9|W|A|X|B|C]]|E|@]|F|$]]|$1|N|3|-4|5|6|7|Y|8|@]|E|@]|F|$]]]|O|$]]

As a note: if you would like to have Server-Side Rendering (SSR), type No and set up your <code>rewrites</code> as follow:

<pre><code>"rewrites": [
 {
 "function": "angularUniversalFunction",
 "source": "**"
 }
]
</code></pre>

After all, whatever you will choose you can always change this in a firebase.json file.

blocks|key|1283312|text|如果您将其设置为“是”，那么所有像www.example.com/some-invalid-url这样的无效URL都将被重定向到站点的index.html，这是一件好事。您还可以将其设置为自定义404.html。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1283313|firebase.json|BOLD|1283314|{|1283315|++"hosting":+{
++++"public":+"pubic",
++++"ignore":+["firebase.json",+"**/.*",+"**/node_modules/**"],
++++"rewrites":+[
++++++{
++++++++"source":+"**",
++++++++"destination":+"/index.html"
++++++}
++++],
++++"cleanUrls":+true
++}
}|code-block|syntax|javascript|1283316|奖励:将cleanUrls设置为true以从部署的网站urls中删除.html扩展，否则所有没有.html的urls都将重定向到index.html。|1283317|entityMap^0|H|W|1V|A|2P|8|0|0|D|0|0|0|4|9|G|4|Y|5|1C|5|1S|A|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|13|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|14|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|S|$]]

If you set it to yes, then all invalid URLs like <code>www.example.com/some-invalid-url</code> will be redirected to <code>index.html</code> of your site which is a good thing. You can also set it to your custom <code>404.html</code>.

firebase.json

{

<pre><code> "hosting": {
 "public": "pubic",
 "ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
 "rewrites": [
 {
 "source": "**",
 "destination": "/index.html"
 }
 ],
 "cleanUrls": true
 }
}
</code></pre>

Bonus: set the <code>cleanUrls</code> to <code>true</code> to remove <code>.html</code> extensions from your deployed website urls else all urls without <code>.html</code> will redirect to <code>index.html</code>.

I just used the Firebase CLI to init a static hosting project. What exactly happens when you enable the "configure as a single-page app" option? I'm looking for a description of exactly which files are modified, and what kind of effect this has on the Firebase backend. 

<a href="https://i.stack.imgur.com/eWIZy.png" rel="noreferrer"><img src="https://i.stack.imgur.com/eWIZy.png" alt="Screenshot of firebase init command"></a>

Firebase CLI: "Configure as a single-page app (rewrite all urls to /index.html)"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我只是使用Firebase CLI在一个静态托管项目中。当您启用“配置为单页应用程序”选项时，会发生什么？我正在寻找一个确切的描述哪些文件被修改，以及这会对Firebase后端产生什么样的影响。​​

问Firebase：“配置为一个单页应用程序(将所有urls重写到/index.html)”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Firebase：“配置为一个单页应用程序(将所有urls重写到/index.html)”EN