By default, **FastAPI** will create a `server` in the OpenAPI schema with the URL for the `root_path`.

But you can also provide other alternative `servers`, for example if you want *the same* docs UI to interact with both a staging and a production environment.

If you pass a custom list of `servers` and there's a `root_path` (because your API lives behind a proxy), **FastAPI** will insert a "server" with this `root_path` at the beginning of the list.

        }
    }

    // Test environment title variations
    public void xtest_environmentTitleVariations() {
        String[] titles = { "Local Development", "Integration Test", "Staging Environment", "Production", "災害復旧環境" };

        for (String title : titles) {
            FessEnv.SimpleImpl titleEnv = new FessEnv.SimpleImpl() {
                protected Properties prepareProperties() {

aizuwakamatsu.fukushima.jp
aju.br
ak.us
akabira.hokkaido.jp
akadns.net
akagi.shimane.jp
akaiwa.okayama.jp
akamai-staging.net
akamai.net
akamaiedge-staging.net
akamaiedge.net
akamaihd-staging.net
akamaihd.net
akamaiorigin-staging.net
akamaiorigin.net
akamaized-staging.net
akamaized.net
akashi.hyogo.jp
akdn
aki.kochi.jp
akiruno.tokyo.jp
akishima.tokyo.jp
akita.akita.jp
akita.jp

{
    "openapi": "3.0.2",
    // More stuff here
    "servers": [
        {
            "url": "/api/v1"
        },
        {
            "url": "https://stag.example.com",
            "description": "Staging environment"
        },
        {
            "url": "https://prod.example.com",
            "description": "Production environment"
        }
    ],
    "paths": {
            // More stuff here

## 附加的服务器

/// warning | 警告

此用例较难，可以跳过。

///

默认情况下，**FastAPI** 使用 `root_path` 的链接在 OpenAPI 概图中创建 `server`。

但也可以使用其它备选 `servers`，例如，需要同一个 API 文档与 staging 和生产环境交互。

如果传递自定义 `servers` 列表，并有 `root_path`（ 因为 API 使用了代理），**FastAPI** 会在列表开头使用这个 `root_path` 插入**服务器**。

例如：

{* ../../docs_src/behind_a_proxy/tutorial003.py hl[4:7] *}

这段代码生产如下 OpenAPI 概图：

Sie können aber auch andere alternative `server` bereitstellen, beispielsweise wenn Sie möchten, dass *dieselbe* Dokumentationsoberfläche mit einer Staging- und Produktionsumgebung interagiert.

          <Prefix>*/_temporary</Prefix>
        </ExcludedPrefixes>
        <ExcludedPrefixes>
          <Prefix>*/__magic</Prefix>
        </ExcludedPrefixes>
        <ExcludedPrefixes>
          <Prefix>*/_staging</Prefix>
        </ExcludedPrefixes>

        <!-- .. up to 10 prefixes in all -->
</VersioningConfiguration>
```

### Features

aizuwakamatsu.fukushima.jp
aju.br
ak.us
akabira.hokkaido.jp
akadns.net
akagi.shimane.jp
akaiwa.okayama.jp
akamai-staging.net
akamai.net
akamaiedge-staging.net
akamaiedge.net
akamaihd-staging.net
akamaihd.net
akamaiorigin-staging.net
akamaiorigin.net
akamaized-staging.net
akamaized.net
akashi.hyogo.jp
akdn
aki.kochi.jp
akiruno.tokyo.jp
akishima.tokyo.jp
akita.akita.jp
akita.jp

akadns.net
akamai.net
akamai-staging.net
akamaiedge.net
akamaiedge-staging.net
akamaihd.net
akamaihd-staging.net
akamaiorigin.net
akamaiorigin-staging.net
akamaized.net
akamaized-staging.net
edgekey.net
edgekey-staging.net
edgesuite.net
edgesuite-staging.net

// alboto.ca : http://alboto.ca

- Crane digest gcr.io/k8s-staging-e2e-test-images/agnhost:2.56 ([#132117](https://github.com/kubernetes/kubernetes/pull/132117), [@yashsingh74](https://github.com/yashsingh74)) [SIG Network and Testing]