OpenAPI şu security scheme’lerini tanımlar:

* `apiKey`: uygulamaya özel bir anahtar; şuradan gelebilir:
    * Bir query parameter.
    * Bir header.
    * Bir cookie.
* `http`: standart HTTP authentication sistemleri, örneğin:
    * `bearer`: `Authorization` header’ı; değeri `Bearer ` + bir token olacak şekilde. Bu, OAuth2’den gelir.

	</component>
	<component name="crawlingInfoHelper" class="org.codelibs.fess.helper.CrawlingInfoHelper">
	</component>
	<component name="roleQueryHelper" class="org.codelibs.fess.helper.RoleQueryHelper">
		<!-- ex. parameter: fessRoles=123%0aRadmin -->
		<!-- 
		<property name="parameterKey">"fessRoles"</property>
		<property name="encryptedParameterValue">false</property>
		<property name="headerKey">"fessRoles"</property>

 * verify() method, which is called after each sequence and is guaranteed to be called
 * using the latest values obtained from {@link IteratorTester#newTargetIterator()}.
 *
 * <p>The value you pass to the parameter {@code steps} should be greater than the length of your
 * iterator, so that this class can check that your iterator behaves correctly when it is exhausted.
 *

            "A duplicate name exists on the network.", "The network name cannot be found.", "ERRnomoreconn.", "The file exists.",
            "The parameter is incorrect.", "Too many Uids active on this session.",
            "The Uid is not known as a valid user identifier on this session.", "The pipe has been ended.",

            "A duplicate name exists on the network.", "The network name cannot be found.", "ERRnomoreconn.", "The file exists.",
            "The parameter is incorrect.", "Too many Uids active on this session.",
            "The Uid is not known as a valid user identifier on this session.", "The pipe has been ended.",

## Request and Response

MinIO will make a `POST` request with a JSON body to the given plugin URL. If the auth token parameter is set, it will be sent as an authorization header.

The JSON body structure can be seen from this sample:

<details><summary>Request Body Sample</summary>

```json
{
  "input": {
    "account": "minio",

            factory.setFeature("http://xml.org/sax/features/external-general-entities", false);
            factory.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
        } catch (SAXNotRecognizedException | SAXNotSupportedException e) {
            throw new SAXRuntimeException(e);
        } catch (final ParserConfigurationException e) {

# 쿼리 매개변수 모델 { #query-parameter-models }

연관된 **쿼리 매개변수** 그룹이 있다면 이를 선언하기 위해 **Pydantic 모델**을 생성할 수 있습니다.

이렇게 하면 **여러 곳**에서 **모델을 재사용**할 수 있을 뿐만 아니라, 매개변수에 대한 검증 및 메타데이터도 한 번에 선언할 수 있습니다. 😎

/// note | 참고

이 기능은 FastAPI 버전 `0.115.0`부터 지원됩니다. 🤓

///

## Pydantic 모델과 쿼리 매개변수 { #query-parameters-with-a-pydantic-model }

필요한 **쿼리 매개변수**를 **Pydantic 모델** 안에 선언한 다음, 매개변수를 `Query`로 선언합니다:

# 回應標頭 { #response-headers }

## 使用 `Response` 參數 { #use-a-response-parameter }

你可以在你的*路徑操作函式（path operation function）*中宣告一個 `Response` 型別的參數（就像處理 Cookie 一樣）。

然後你可以在那個*暫時性的* `Response` 物件上設定標頭。

{* ../../docs_src/response_headers/tutorial002_py310.py hl[1, 7:8] *}

接著你可以像平常一樣回傳任何你需要的物件（`dict`、資料庫模型等）。

如果你宣告了 `response_model`，它仍會用來過濾並轉換你回傳的物件。

FastAPI 會使用那個暫時性的回應來擷取標頭（還有 Cookie 與狀態碼），並把它們放到最終回應中；最終回應包含你回傳的值，且會依任何 `response_model` 進行過濾。

   * {@link #splitToList(CharSequence)}.
   *
   * @param sequence the sequence of characters to split
   * @return an iteration over the segments split from the parameter
   */
  public Iterable<String> split(CharSequence sequence) {
    checkNotNull(sequence);

    return new Iterable<String>() {
      @Override
      public Iterator<String> iterator() {