`from starlette.responses import JSONResponse`를 사용할 수도 있습니다.

**FastAPI**는 개발자의 편의를 위해 `starlette.responses`를 `fastapi.responses`로 제공합니다. 하지만 대부분의 사용 가능한 응답은 Starlette에서 직접 제공합니다.

///

## 사용자 정의 `Response` 반환하기 { #returning-a-custom-response }

위 예제는 필요한 모든 부분을 보여주지만, 아직은 그다지 유용하지 않습니다. `item`을 그냥 직접 반환했어도 **FastAPI**가 기본으로 이를 `JSONResponse`에 넣고 `dict`로 변환하는 등의 작업을 모두 수행해 주었을 것이기 때문입니다.

이제, 이를 사용해 사용자 정의 응답을 반환하는 방법을 알아보겠습니다.

/// note | 技术细节

你也可以使用 `from starlette.responses import JSONResponse`。

出于方便，**FastAPI** 会提供与 `starlette.responses` 相同的 `fastapi.responses` 给开发者。但是大多数可用的响应都直接来自 Starlette。

///

## 返回自定义 `Response` { #returning-a-custom-response }

上面的例子展示了需要的所有部分，但还不够实用，因为你本可以只是直接返回 `item`，而 **FastAPI** 默认帮你把这个 `item` 放到 `JSONResponse` 中，又默认将其转换成了 `dict` 等等。

现在，让我们看看你如何才能返回一个自定义的响应。

假设你想要返回一个 [XML](https://en.wikipedia.org/wiki/XML) 响应。

### Creando el `Settings` solo una vez con `lru_cache` { #creating-the-settings-only-once-with-lru-cache }

Leer un archivo desde el disco es normalmente una operación costosa (lenta), por lo que probablemente quieras hacerlo solo una vez y luego reutilizar el mismo objeto de configuraciones, en lugar de leerlo para cada request.

Pero cada vez que hacemos:

```Python
Settings()
```

        record(keyObj, action.name().toLowerCase(Locale.ENGLISH));
    }

    /**
     * Records a custom statistics action for the specified crawler object.
     *
     * @param keyObj the crawler object being tracked
     * @param action the custom action name to record
     */
    public void record(final Object keyObj, final String action) {
        getCacheKey(keyObj).ifPresent(key -> {

        // Create a custom NetworkExplorer that bypasses resource loading
        networkExplorer = createMockedNetworkExplorer(false, "jCIFS");

        assertDoesNotThrow(() -> networkExplorer.init(servletConfig));
    }

    /**
     * Test servlet initialization with custom JCIFS parameters
     */
    @Test

            data["client_secret"] = form_data.client_secret
        return data
    ```

    Note that for OAuth2 the scope `items:read` is a single scope in an opaque string.
    You could have custom internal logic to separate it by colon characters (`:`) or
    similar, and get the two parts `items` and `read`. Many applications do that to
    group and organize permissions, you could do it as well in your application, just

Following is a sample directory structure for MinIO server with TLS certificates.

```sh
$ mc tree --files ~/.minio
/home/user1/.minio
└─ certs
   ├─ CAs
   ├─ private.key
   └─ public.crt
```

You can provide a custom certs directory using `--certs-dir` command line option.

#### Credentials

On MinIO admin credentials or root credentials are only allowed to be changed using ENVs namely `MINIO_ROOT_USER` and `MINIO_ROOT_PASSWORD`.

        final CreateForm form = new CreateForm();
        form.doc = new HashMap<>();
        form.doc.put("url", "https://example.com");
        form.doc.put("title", "Test");
        form.doc.put("custom_metadata", "custom value");
        form.doc.put("department", "Engineering");

        final java.lang.reflect.Field currentFormField = AdminSearchlistAction.class.getDeclaredField("currentForm");
        currentFormField.setAccessible(true);

// functions are defined in this package for scanning a file into
// lines, bytes, UTF-8-encoded runes, and space-delimited words. The
// client may instead provide a custom split function.
//
// Scanning stops unrecoverably at EOF, the first I/O error, or a token too
// large to fit in the [Scanner.Buffer]. When a scan stops, the reader may have

        if (lookup == null) {
            return customLifecycles != null ? customLifecycles : new HashMap<>();
        }

        // Lifecycles cannot be cached as extensions might add custom lifecycles later in the execution.
        try {
            return registry != null
                    ? registry.stream().collect(Collectors.toMap(lf -> lf.id(), lf -> new Lifecycle(registry, lf)))