Das ist keine Limitation von **FastAPI**, sondern Teil des HTTP-Protokolls.

///

## Zusammenfassung { #recap }

      ),
    )

    val request1 = Request.Builder().url(server.url("/")).build()
    val response1 = client.newCall(request1).execute()
    assertThat(response1.code).isEqualTo(401)
    assertThat(response1.body.string())
      .isEqualTo("{\"error\":{\"message\":\"No auth credentials found\",\"code\":401}}")

    val request2 = request1.newBuilder().header("Authorization", "XYZ").build()

## Проверьте документацию { #check-the-docs }

Вы можете проверить это в интерфейсе документации по адресу `/docs`:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Запрет дополнительных полей формы { #forbid-extra-form-fields }

# Request Forms and Files { #request-forms-and-files }

You can define files and form fields at the same time using `File` and `Form`.

/// info

To receive uploaded files and/or form data, first install [`python-multipart`](https://github.com/Kludex/python-multipart).

Make sure you create a [virtual environment](../virtual-environments.md), activate it, and then install it, for example:

```console
$ pip install python-multipart
```

///

 * [RFC 2817][1]. The HTTP CONNECT request that creates this tunnel connection is special: it
 * does not participate in any [interceptors][Interceptor] or [event listeners][EventListener]. It
 * doesn't include the motivating request's HTTP headers or even its full URL; only the target
 * server's hostname is sent to the proxy.
 *
 * Prior to sending any CONNECT request OkHttp always calls the proxy authenticator so that it may

**FastAPI** はリクエストの **フォームデータ** から **各フィールド** のデータを **抽出** し、定義した Pydantic モデルとして渡します。

## ドキュメントで確認 { #check-the-docs }

`/docs` のドキュメント UI で確認できます:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## 追加のフォームフィールドを禁止 { #forbid-extra-form-fields }

一部の特殊なユースケース（おそらくあまり一般的ではありません）では、フォームフィールドを Pydantic モデルで宣言したもののみに**制限**し、**追加**のフィールドを**禁止**したい場合があります。

/// note | 備考

 */
package jcifs.internal;

import jcifs.CIFSContext;

/**
 * Generic interface for typed SMB request messages.
 * Extends the common request interface with type-safe response handling,
 * allowing requests to specify their expected response type.
 *
 * @author mbechler
 * @param <T> response type
 */
public interface Request<T extends CommonServerMessageBlockResponse> extends CommonServerMessageBlockRequest {

    /**

package jcifs.smb1.util.transport;

/**
 * Marker interface for transport layer request objects.
 * Represents a request that can be sent through the SMB1 transport layer.
 */
public interface Request {

/// note | 技術細節

`Request` 具有 `request.scope` 屬性，它其實就是一個 Python 的 `dict`，包含與該請求相關的中繼資料。

`Request` 也有 `request.receive`，那是一個用來「接收」請求本文的函式。

`scope` 這個 `dict` 與 `receive` 函式都是 ASGI 規格的一部分。

而 `scope` 與 `receive` 這兩者，就是建立一個新的 `Request` 實例所需的資料。

想了解更多 `Request`，請參考 [Starlette 的 Request 文件](https://www.starlette.dev/requests/)。

///

import jcifs.Encodable;
import jcifs.internal.util.SMBUtil;

/**
 * DFS (Distributed File System) referral request buffer encoder.
 * Creates encoded request buffers for DFS referral requests, specifying the maximum
 * referral level and target path for which DFS resolution is requested.
 *
 * @author mbechler
 */
public class DfsReferralRequestBuffer implements Encodable {

    private final int maxReferralLevel;