From a939f44e37fddcb1954d509838cbb41fc8afe5cb Mon Sep 17 00:00:00 2001 From: wxiaoguang Date: Tue, 14 Apr 2026 16:08:45 +0800 Subject: [PATCH] fix typo # Conflicts: # docs/administration/reverse-proxies.md --- docs/administration/reverse-proxies.md | 4 ++-- .../version-1.23/administration/reverse-proxies.md | 2 +- versioned_docs/version-1.22/administration/reverse-proxies.md | 2 +- versioned_docs/version-1.23/administration/reverse-proxies.md | 2 +- versioned_docs/version-1.24/administration/reverse-proxies.md | 2 +- versioned_docs/version-1.25/administration/reverse-proxies.md | 4 ++-- versioned_docs/version-1.26/administration/reverse-proxies.md | 4 ++-- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/administration/reverse-proxies.md b/docs/administration/reverse-proxies.md index 72739017..6e10a60d 100644 --- a/docs/administration/reverse-proxies.md +++ b/docs/administration/reverse-proxies.md @@ -13,8 +13,8 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. -5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. ### Use a sub-path diff --git a/i18n/zh-tw/docusaurus-plugin-content-docs/version-1.23/administration/reverse-proxies.md b/i18n/zh-tw/docusaurus-plugin-content-docs/version-1.23/administration/reverse-proxies.md index 34803501..4c0044b3 100644 --- a/i18n/zh-tw/docusaurus-plugin-content-docs/version-1.23/administration/reverse-proxies.md +++ b/i18n/zh-tw/docusaurus-plugin-content-docs/version-1.23/administration/reverse-proxies.md @@ -13,7 +13,7 @@ aliases: 1. 在您的 `app.ini` 文件中設置 `[server] ROOT_URL = https://git.example.com/`。 2. 使反向代理將 `https://git.example.com/foo` 傳遞到 `http://gitea:3000/foo`。 3. 確保反向代理不解碼 URI。請求 `https://git.example.com/a%2Fb` 應傳遞為 `http://gitea:3000/a%2Fb`。 -4. 確保 `Host` 和 `X-Fowarded-Proto` 標頭正確傳遞給 Gitea，以使 Gitea 看到實際訪問的 URL。 +4. 確保 `Host` 和 `X-Forwarded-Proto` 標頭正確傳遞給 Gitea，以使 Gitea 看到實際訪問的 URL。 ### 使用子路徑 diff --git a/versioned_docs/version-1.22/administration/reverse-proxies.md b/versioned_docs/version-1.22/administration/reverse-proxies.md index b81dfbc3..d3deb755 100644 --- a/versioned_docs/version-1.22/administration/reverse-proxies.md +++ b/versioned_docs/version-1.22/administration/reverse-proxies.md @@ -15,7 +15,7 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. ### Use a sub-path diff --git a/versioned_docs/version-1.23/administration/reverse-proxies.md b/versioned_docs/version-1.23/administration/reverse-proxies.md index e248cc5e..fa65f7b9 100644 --- a/versioned_docs/version-1.23/administration/reverse-proxies.md +++ b/versioned_docs/version-1.23/administration/reverse-proxies.md @@ -13,7 +13,7 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. ### Use a sub-path diff --git a/versioned_docs/version-1.24/administration/reverse-proxies.md b/versioned_docs/version-1.24/administration/reverse-proxies.md index e248cc5e..fa65f7b9 100644 --- a/versioned_docs/version-1.24/administration/reverse-proxies.md +++ b/versioned_docs/version-1.24/administration/reverse-proxies.md @@ -13,7 +13,7 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. ### Use a sub-path diff --git a/versioned_docs/version-1.25/administration/reverse-proxies.md b/versioned_docs/version-1.25/administration/reverse-proxies.md index 353c0056..aaa51354 100644 --- a/versioned_docs/version-1.25/administration/reverse-proxies.md +++ b/versioned_docs/version-1.25/administration/reverse-proxies.md @@ -13,8 +13,8 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. -5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. ### Use a sub-path diff --git a/versioned_docs/version-1.26/administration/reverse-proxies.md b/versioned_docs/version-1.26/administration/reverse-proxies.md index 72739017..6e10a60d 100644 --- a/versioned_docs/version-1.26/administration/reverse-proxies.md +++ b/versioned_docs/version-1.26/administration/reverse-proxies.md @@ -13,8 +13,8 @@ aliases: 1. Set `[server] ROOT_URL = https://git.example.com/` in your `app.ini` file. 2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`. 3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`. -4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. -5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. +4. Make sure `Host` and `X-Forwarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited. +5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work. ### Use a sub-path