for (Long count : statsAfter.values()) {
            assertEquals(Long.valueOf(0), count, "All statistics should be 0 after reset");
        }
    }

    @Test
    @DisplayName("Test JSON logging toggle")
    void testJsonLoggingToggle() {
        logger.setJsonLoggingEnabled(true);
        logger.logAuthentication(true, "user", "DOMAIN", "192.168.1.1");

        logger.setJsonLoggingEnabled(false);

     *
     * @param projectId the GCS project ID
     * @param bucket the bucket name
     * @param endpoint the custom endpoint URL (optional, for fake-gcs-server etc.)
     * @param credentialsPath the path to the credentials JSON file (optional)
     */
    public GcsStorageClient(final String projectId, final String bucket, final String endpoint, final String credentialsPath) {
        this.bucket = bucket;

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

その*path operation*と通信する際に、次のように2つのHTTPヘッダーを送信する場合:

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

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

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

## まとめ { #recap }

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

```

you would receive the multiple `q` *query parameters'* values (`foo` and `bar`) in a Python `list` inside your *path operation function*, in the *function parameter* `q`.

So, the response to that URL would be:

```JSON
{
  "q": [
    "foo",
    "bar"
  ]
}
```

/// tip

    for an OAuth2 password flow.

    The OAuth2 specification dictates that for a password flow the data should be
    collected using form data (instead of JSON) and that it should have the specific
    fields `username` and `password`.

    All the initialization parameters are extracted from the request.

    Read more about it in the

import org.opensearch.action.search.SearchResponse;
import org.opensearch.common.xcontent.XContentFactory;
import org.opensearch.common.xcontent.XContentType;
import org.opensearch.common.xcontent.json.JsonXContent;
import org.opensearch.core.xcontent.XContentBuilder;
import org.opensearch.index.IndexNotFoundException;
import org.opensearch.index.query.QueryBuilders;
import org.opensearch.search.SearchHit;

        // always inject compat headers
        headers.put("Content-Type", "application/vnd.elasticsearch+json;compatible-with=" + compatibleVersion);
        headers.put("Accept", "application/vnd.elasticsearch+json;compatible-with=" + compatibleVersion);
        transformations.add(new InjectHeaders(headers, Set.of(RestCompatTestTransformTask::doesNotHaveCatOperation)));
    }

### 1. Update OpenSearch Index Template

Edit `src/main/resources/fess_indices/fess.json` to add language-specific analyzers.

**Example for Swedish:**
```json
{
  "analysis": {
    "filter": {
      "swedish_stop": {
        "type": "stop",
        "stopwords": "_swedish_"
      },
      "swedish_stemmer": {

```sh
mc admin policy create myminio mypolicy mypolicy.json
```

                        .header("Authorization", "Bearer " + user.getAuthenticationResult().accessToken())
                        .header("Accept", "application/json")
                        .header("Content-type", "application/json")
                        .body("{\"securityEnabledOnly\":false}")
                        .execute()) {