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

`/docs` のドキュメント UI で必要なヘッダーを確認できます:

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

## 余分なヘッダーを禁止 { #forbid-extra-headers }

特殊なユースケース（あまり一般的ではありません）では、受け付けるヘッダーを**制限**したい場合があります。

Pydantic のモデル設定で `extra` フィールドを `forbid` にして禁止できます:

{* ../../docs_src/header_param_models/tutorial002_an_py310.py hl[10] *}

    if (opcode == OPCODE_TEXT) {
      frameCallback.onReadMessage(messageFrameBuffer.readUtf8())
    } else {
      frameCallback.onReadMessage(messageFrameBuffer.readByteString())
    }
  }

  /** Read headers and process any control frames until we reach a non-control frame. */
  @Throws(IOException::class)
  private fun readUntilNonControlFrame() {
    while (!receivedCloseFrame) {
      readHeader()

import okhttp3.CallEvent.ResponseHeadersEnd
import okhttp3.CallEvent.ResponseHeadersStart
import okhttp3.CallEvent.SecureConnectEnd
import okhttp3.CallEvent.SecureConnectStart
import okhttp3.Headers.Companion.headersOf
import okhttp3.TestUtil.assumeNotWindows
import okhttp3.internal.duplex.AsyncRequestBody
import okhttp3.testing.PlatformRule
import okio.BufferedSink
import okio.IOException

			}

			// Heal each part. erasure.Heal() will write the healed
			// part to .minio/tmp/uuid/ which needs to be renamed
			// later to the final location.
			err = erasure.Heal(ctx, writers, readers, partSize, prefer)
			closeBitrotReaders(readers)
			closeErrs := closeBitrotWriters(writers)
			if err != nil {
				return result, err
			}

			// outDatedDisks that had write errors should not be

tracebacks.

### Go 1.26

Go 1.26 added a new `httpcookiemaxnum` setting that controls the maximum number
of cookies that net/http will accept when parsing HTTP headers. If the number of
cookie in a header exceeds the number set in `httpcookiemaxnum`, cookie parsing
will fail early. The default value is `httpcookiemaxnum=3000`. Setting

- [Об'єкт відповіді OpenAPI](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#response-object), ви можете включити будь-що з цього безпосередньо в кожну відповідь у параметрі `responses`. Зокрема `description`, `headers`, `content` (усередині нього ви оголошуєте різні типи медіа та Схеми JSON) і `links`....

			}

			// CRC64NVME is always full object
			if chksm.Type.Base().Is(ChecksumCRC64NVME) {
				chksm.Type |= ChecksumFullObject
			}

			// Prepare the checksum map with appropriate headers
			m := chksm.AsMap()
			m[xhttp.AmzChecksumAlgo] = chksm.Type.String() // Set the algorithm explicitly
			if chksm.Type.FullObjectRequested() {
				m[xhttp.AmzChecksumType] = xhttp.AmzChecksumTypeFullObject
			} else {

import org.codelibs.curl.io.ContentOutputStream;

/**
 * The CurlRequest class represents an HTTP request that can be configured and executed.
 * It supports various HTTP methods, request parameters, headers, body content, and more.
 */
public class CurlRequest {

    /**
     * The GZIP compression type.
     */
    protected static final String GZIP = "gzip";

    /**

	UploadID string

	// Date and time at which the multipart upload was initiated.
	Initiated time.Time

	// Any metadata set during InitMultipartUpload, including encryption headers.
	UserDefined map[string]string
}

// ListPartsInfo - represents list of all parts.
type ListPartsInfo struct {
	// Name of the bucket.
	Bucket string

	// Name of the object.
	Object string

## Conceitos de Implantação { #deployment-concepts }

Aqui você viu como usar vários **trabalhadores** para **paralelizar** a execução do aplicativo, aproveitar **vários núcleos** na CPU e conseguir atender **mais solicitações**.

Da lista de conceitos de implantação acima, o uso de trabalhadores ajudaria principalmente com a parte da **replicação** e um pouco com as **reinicializações**, mas você ainda precisa cuidar dos outros: