쿠키 매개변수를 `Query`와 `Path` 매개변수들과 같은 방식으로 정의할 수 있습니다.

## `Cookie` 임포트

먼저 `Cookie`를 임포트합니다:

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

## `Cookie` 매개변수 선언

그런 다음, `Path`와 `Query`처럼 동일한 구조를 사용하는 쿠키 매개변수를 선언합니다.

첫 번째 값은 기본값이며, 추가 검증이나 어노테이션 매개변수 모두 전달할 수 있습니다:

{* ../../docs_src/cookie_params/tutorial001_an_py310.py hl[9] *}

/// note | 기술 세부사항

			return
		}
	} else {
		path := filepath.Join("testdata", zt.Name)
		if zt.Obscured {
			tf, err := obscuretestdata.DecodeToTempFile(path)
			if err != nil {
				t.Errorf("obscuretestdata.DecodeToTempFile(%s): %v", path, err)
				return
			}
			defer os.Remove(tf)
			path = tf
		}
		var rc *ReadCloser
		rc, err = OpenReader(path)
		if err == nil {
			defer rc.Close()

In those cases, you can use the *path operation decorator* parameter `response_model` instead of the return type.

You can use the `response_model` parameter in any of the *path operations*:

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

# Header-параметри

Ви можете визначати параметри заголовків, так само як визначаєте `Query`, `Path` і `Cookie` параметри.

## Імпорт `Header`

Спочатку імпортуйте `Header`:

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

## Оголошення параметрів `Header`

Потім оголосіть параметри заголовків, використовуючи ту ж структуру, що й для `Path`, `Query` та `Cookie`.

    public BaseApiManager() {
        // Default constructor
    }

    /**
     * Gets the path prefix for API endpoints.
     * @return The path prefix.
     */
    public String getPathPrefix() {
        return pathPrefix;
    }

    /**
     * Sets the path prefix for API endpoints.
     * @param pathPrefix The path prefix to set.
     */
    public void setPathPrefix(final String pathPrefix) {

@Experimental
public interface ProjectManager extends Service {
    /**
     * Returns the path to the built project artifact file, if the project has been built.
     * This path is only available after the artifact has been produced during the build lifecycle.
     *
     * @param project the project to get the artifact path for
     * @return an Optional containing the path to the built artifact if available,

# クッキーのパラメータ

クッキーのパラメータは、`Query`や`Path`のパラメータを定義するのと同じ方法で定義できます。

## `Cookie`をインポート

まず、`Cookie`をインポートします:

{* ../../docs_src/cookie_params/tutorial001.py hl[3] *}

## `Cookie`のパラメータを宣言

次に、`Path`や`Query`と同じ構造を使ってクッキーのパラメータを宣言します。

最初の値がデフォルト値で、追加の検証パラメータや注釈パラメータをすべて渡すことができます:

{* ../../docs_src/cookie_params/tutorial001.py hl[9] *}

/// note | 技術詳細

`Cookie`は`Path`と`Query`の「姉妹」クラスです。また、同じ共通の`Param`クラスを継承しています。

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.user.User" />

        assertTrue(confPath.toString().contains("file.conf"));
    }

    public void test_getConfOrClassesPath() {
        // Test behavior when resource is not found
        try {
            Path path = ResourceUtil.getConfOrClassesPath("nonexistent.conf");
            fail("Should throw ResourceNotFoundRuntimeException for non-existent file");
        } catch (org.codelibs.core.exception.ResourceNotFoundRuntimeException e) {

                                    </tr>
                                    <tr>
                                        <th><la:message key="labels.paths"/></th>
                                        <td>${f:br(f:h(paths))}<la:hidden property="paths"/></td>
                                    </tr>
                                    <tr>
                                        <th><la:message key="labels.included_paths"/></th>