```TypeScript
ItemsService.createItemItemsPost({name: "Plumbus", price: 5})
```

...çünkü client üreteci, her *path operation* için OpenAPI'nin dahili **operation ID** değerini kullanır.

OpenAPI, her operation ID'nin tüm *path operation*'lar arasında benzersiz olmasını ister. Bu yüzden FastAPI; operation ID'yi benzersiz tutabilmek için **function adı**, **path** ve **HTTP method/operation** bilgilerini birleştirerek üretir.

 *     <li>{@linkplain org.apache.maven.api.services.ProjectManager#attachArtifact(Session, Project, Path) artifacts to be attached to a project}</li>
 * </ul>
 *
 * <p>For the main artifact and attached artifacts, the
 * {@link org.apache.maven.api.services.ArtifactManager ArtifactManager} service must be used
 * to point the artifact to a {@link Path} during the packaging phase.</p>
 *
 * @since 4.0.0
 * @see Project#getMainArtifact()

 * This form is used in the admin API interface to upload files to the storage backend
 * with optional path specification for file organization.
 */
public class UploadForm {

    /**
     * The storage path where the file should be uploaded.
     * If not specified, the file will be stored in the default location.
     */
    public String path;

    /**
     * The multipart file to be uploaded to the storage system.

For that you need to access the request directly.

{* ../../docs_src/using_request_directly/tutorial001_py310.py hl[1,7:8] *}

By declaring a *path operation function* parameter with the type being the `Request` **FastAPI** will know to pass the `Request` in that parameter.

/// tip

Note that in this case, we are declaring a path parameter beside the request parameter.

* include: включать (add `в себя` if it's appropriate, or use `содержать` as an alternative)
* virtual environment: виртуальное окружение
* framework: фреймворк
* path paremeter: path-параметр
* path (as in URL path): путь
* form (as in HTML form): форма
* media type: тип содержимого (or `медиа-тип`)
* request: HTTP-запрос
* response: HTTP-ответ
* type hints: аннотации типов

Sie können Header-Parameter genauso definieren, wie Sie `Query`-, `Path`- und `Cookie`-Parameter definieren.

## `Header` importieren { #import-header }

Importieren Sie zuerst `Header`:

{* ../../docs_src/header_params/tutorial001_an_py310.py hl[3] *}

## `Header`-Parameter deklarieren { #declare-header-parameters }

Deklarieren Sie dann die Header-Parameter mit derselben Struktur wie bei `Path`, `Query` und `Cookie`.

## Déprécier un *chemin d'accès* dans la documentation - OpenAPI { #documentation-deprecate-a-path-operation-openapi }

Pour déprécier un *chemin d'accès* et l'indiquer dans l'interface utilisateur de la documentation, lisez les documents [Tutoriel - Configurations de chemin d'accès - Dépréciation](../tutorial/path-operation-configuration.md#deprecate-a-path-operation).

`Header` 是 `Path`、`Query`、`Cookie` 的**兄弟类**，都继承自共用的 `Param` 类。

注意，从 `fastapi` 导入的 `Query`、`Path`、`Header` 等对象，实际上是返回特殊类的函数。

///

/// info | 信息

必须使用 `Header` 声明 header 参数，否则该参数会被解释为查询参数。

///

## 自动转换 { #automatic-conversion }

`Header` 比 `Path`、`Query` 和 `Cookie` 提供了更多功能。

大部分标准请求头用**连字符**分隔，即**减号**（`-`）。

但是 `user-agent` 这样的变量在 Python 中是无效的。

因此，默认情况下，`Header` 把参数名中的字符由下划线（`_`）改为连字符（`-`）来提取并存档请求头 。

Si hay un query en el request, se escribirá en el log en una tarea en segundo plano.

Y luego otra tarea en segundo plano generada en la *path operation function* escribirá un mensaje usando el parámetro de path `email`.

## Detalles Técnicos { #technical-details }

La clase `BackgroundTasks` proviene directamente de [`starlette.background`](https://www.starlette.dev/background/).

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute.xml" />
	
	<!-- Register systemProperties for test environment -->
	<component name="systemProperties" class="org.codelibs.fess.unit.TestSystemProperties" />