| *Valid Range* | *Minimum value of 900. Maximum value of 31536000.* |
| *Required*    | *No*                                               |

### Policy

labels.searchLog=搜尋日誌
labels.sort=排序
labels.start=開始位置
labels.loginRequired=需要登入
labels.loginLink=顯示登入連結
labels.threadName=執行緒名稱
labels.url=URL
labels.userFavorite=收藏日誌
labels.userInfo=使用者資訊
labels.webApiJson=JSON響應
labels.webConfigName=Web爬網配置名稱
labels.allLanguages=所有語言
labels.dictId=字典ID
labels.docId=文檔ID
labels.endTime=結束時間
labels.hq=hq
labels.inputs=輸入
labels.jobLogging=日誌記錄
labels.jobName=名稱
labels.jobStatus=狀態

this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not
correct.
Other client authors should double check that you are sending proper
accept and content type headers, or set no value (in which case JSON is the
default).
An example using curl:
<code>curl -H "Content-Type: application/json" -XPOST -d

    return {"fresh_value": fresh_value}
```

////

## Resumen

Aparte de todas las palabras rimbombantes usadas aquí, el sistema de **Inyección de Dependencias** es bastante simple.

Solo son funciones que se ven igual que las *path operation functions*.

Pero aun así, es muy potente y te permite declarar "grafos" de dependencia anidados arbitrariamente profundos (árboles).

/// tip | Consejo

github.com/gobwas/ws v1.4.0 h1:CTaoG1tojrh4ucGPcoJFiAQUAsEWekEWvLy7GsVNqGs=
github.com/gobwas/ws v1.4.0/go.mod h1:G3gNqMNtPppf5XUz7O4shetPpcZ1VJ7zt18dlUeakrc=
github.com/goccy/go-json v0.10.5 h1:Fq85nIqj+gXn/S5ahsiTlK3TmC85qgirsdTP/+DeaC4=
github.com/goccy/go-json v0.10.5/go.mod h1:oq7eo15ShAhp70Anwd5lgX2pLfOS3QCiwU/PULtXL6M=
github.com/godbus/dbus/v5 v5.0.4/go.mod h1:xhWf0FNVPg57R7Z0UbKHbJfkEywrmjJnf7w5xrFpKfA=

api.search.accept.referers=
# Whether to enable scroll for API search.
api.search.scroll=false
# Headers for API JSON response.
api.json.response.headers=Referrer-Policy:strict-origin-when-cross-origin
# Whether to include exceptions in API JSON response.
api.json.response.exception.included=false
# Headers for API GSA response.
api.gsa.response.headers=Referrer-Policy:strict-origin-when-cross-origin

import org.junit.jupiter.api.BeforeAll;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Tag;
import org.junit.jupiter.api.Test;

import io.restassured.RestAssured;
import io.restassured.path.json.JsonPath;

/**
 * Integration Tests which need an execution of crawler
 * - /api/admin/joblog
 * - /api/admin/crawlinginfo
 * - /api/admin/failureurl
 * - /api/admin/searchlist
 * */
@Tag("it")

{* ../../docs_src/header_params/tutorial003.py hl[9] *}

もし、その*path operation*で通信する場合は、次のように２つのHTTPヘッダーを送信します:

```
X-Token: foo
X-Token: bar
```

このレスポンスは以下のようになります:

```JSON
{
    "X-Token values": [
        "bar",
        "foo"
    ]
}
```

## まとめ

ヘッダーは`Header`で宣言し、`Query`や`Path`、`Cookie`と同じパターンを使用する。

## Dependencies

### Added
_Nothing has changed._

### Changed
- github.com/evanphx/json-patch: [162e562 → v4.9.0+incompatible](https://github.com/evanphx/json-patch/compare/162e562...v4.9.0)

### Removed
- github.com/jessevdk/go-flags: [v1.4.0](https://github.com/jessevdk/go-flags/tree/v1.4.0)



# v1.17.11

    }

    public void test_exceptionWithSpecialCharactersInMessage() {
        // Test with special characters in message
        int statusCode = 400;
        String message = "Error: \"Invalid JSON\" - {key: 'value'} \n\t@#$%^&*()";

        WebApiException exception = new WebApiException(statusCode, message);

        assertEquals(statusCode, exception.getStatusCode());