그러나 폼에 파일이 포함된 경우, `multipart/form-data`로 인코딩합니다. 다음 장에서 파일 처리에 대해 읽을 겁니다.

이러한 인코딩 및 폼 필드에 대해 더 읽고 싶다면, [`POST`에 대한 <abbr title="Mozilla Developer Network - Mozilla 개발자 네트워크">MDN</abbr> 웹 문서를 참조하세요](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST).

///

/// warning | 경고

        final ResponseData responseData = new ResponseData();

        responseData.setMethod("GET");
        assertEquals("GET", responseData.getMethod());

        responseData.setMethod("POST");
        assertEquals("POST", responseData.getMethod());
    }

    @Test
    public void test_responseData_metaDataMap() {
        final ResponseData responseData = new ResponseData();

                    final String value;
                    final int pos = s.indexOf('=');
                    if (pos == -1 || pos == s.length() - 1) {
                        name = s;
                        value = StringUtil.EMPTY;
                    } else {
                        name = s.substring(0, pos);
                        value = s.substring(pos + 1);
                    }

当连接中断后浏览器重新连接时，会在 `Last-Event-ID` 头中发送上次收到的 `id`。

你可以将其读取为一个请求头参数，并据此从客户端离开的地方恢复流：

{* ../../docs_src/server_sent_events/tutorial004_py310.py hl[25,27,31] *}

## 使用 POST 的 SSE { #sse-with-post }

SSE 适用于**任意 HTTP 方法**，不仅仅是 `GET`。

这对像 [MCP](https://modelcontextprotocol.io) 这样通过 `POST` 传输 SSE 的协议很有用：

{* ../../docs_src/server_sent_events/tutorial005_py310.py hl[14] *}

## 技术细节 { #technical-details }

FastAPI 开箱即用地实现了一些 SSE 的最佳实践。

    # Update the viewport manually
    context = browser.new_context(viewport={"width": 960, "height": 1080})
    page = context.new_page()
    page.goto("http://localhost:8000/docs")
    page.get_by_label("post /heroes/").click()
    # Manually add the screenshot
    page.screenshot(path="docs/en/docs/img/tutorial/sql-databases/image02.png")

    # ---------------------
    context.close()
    browser.close()

     * @param dictId the dictionary ID
     * @param body the request body containing Kuromoji item information
     * @return JSON response with result status
     */
    // POST /api/admin/dict/kuromoji/setting/{dictId}
    @Execute
    public JsonResponse<ApiResult> post$setting(final String dictId, final CreateBody body) {
        body.dictId = dictId;
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;

     * @param body create request payload
     * @return JSON response containing creation result and new entry ID
     */
    // POST /api/admin/dict/protwords/setting/{dictId}
    @Execute
    public JsonResponse<ApiResult> post$setting(final String dictId, final CreateBody body) {
        body.dictId = dictId;
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;

        })).status(Status.OK).result());
    }

    // POST /api/admin/accesstoken/setting
    /**
     * Creates a new access token setting.
     *
     * @param body the create body containing access token data
     * @return JSON response with the created access token ID
     */
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});

## REST API call to plugin

To verify the custom token presented in the `AssumeRoleWithCustomToken` API, MinIO makes a POST request to the configured identity management plugin endpoint and expects a response with some details as shown below:

### Request `POST` to plugin endpoint

Query parameters:

| Parameter Name | Value Type | Purpose                                                                 |

    }

    /**
     * Creates a POST request for the specified path.
     * @param path the request path
     * @return the configured CurlRequest
     */
    public CurlRequest post(final String path) {
        return request(Method.POST, path).header("Content-Type", "application/json");
    }

    /**