# Réponse - Modifier le code d'état { #response-change-status-code }

Vous avez probablement déjà lu que vous pouvez définir un [Code d'état de la réponse](../tutorial/response-status-code.md) par défaut.

Mais dans certains cas, vous devez renvoyer un code d'état différent de celui par défaut.

## Cas d'utilisation { #use-case }

Par exemple, imaginez que vous vouliez renvoyer par défaut un code d'état HTTP « OK » `200`.

# Retorno - Altere o Código de Status { #response-change-status-code }

Você provavelmente leu anteriormente que você pode definir um [Código de Status do Retorno](../tutorial/response-status-code.md) padrão.

Porém em alguns casos você precisa retornar um código de status diferente do padrão.

## Caso de uso { #use-case }

Por exemplo, imagine que você deseja retornar um código de status HTTP de "OK" `200` por padrão.

# 回應 - 變更狀態碼 { #response-change-status-code }

你可能已經讀過，可以設定預設的[回應狀態碼](../tutorial/response-status-code.md)。

但有些情況你需要回傳與預設不同的狀態碼。

## 使用情境 { #use-case }

例如，假設你預設想回傳 HTTP 狀態碼 "OK" `200`。

但如果資料不存在，你想要建立它，並回傳 HTTP 狀態碼 "CREATED" `201`。

同時你仍希望能用 `response_model` 過濾並轉換所回傳的資料。

在這些情況下，你可以使用 `Response` 參數。

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

    /**
     * Any file name change in the watched directory or subtree causes a change notification wait operation to return.
     * Changes include renaming, creating, or deleting a file.
     */
    int FILE_NOTIFY_CHANGE_FILE_NAME = 0x00000001;

    /**
     * Any directory-name change in the watched directory or subtree causes a change notification wait operation to
     * return. Changes include creating or deleting a directory.

## Motivation and Context


## How to test this PR?


## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Optimization (provides speedup with no functional changes)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

## Checklist:

    print "\n${team}::\n";

    for (change in changelogsByVersionByTypeByArea[version][changeType][team]) {
        print "* ${change.summary} {es-pull}${change.pr}[#${change.pr}]"
        if (change.issues != null && change.issues.empty == false) {
            print change.issues.size() == 1 ? " (issue: " : " (issues: "
            print change.issues.collect { "{es-issue}${it}[#${it}]" }.join(", ")
            print ")"

                try {
                    // Note: Actual SMB2 Change Notify implementation would go here
                    // For now, this is a placeholder that simulates monitoring

                    // In a real implementation, we would:
                    // 1. Send SMB2 Change Notify request
                    // 2. Wait for response
                    // 3. Process changes
                    // 4. Notify the lease manager

    public void test_changePassword_success() {
        // Test successful password change when LDAP admin sync is disabled
        testLdapManager.changePasswordResult = true;
        testFessConfig.ldapAdminSyncPassword = false;

        boolean result = ldapChain.changePassword("testuser", "newpassword");

        assertFalse(result); // returns !changed || syncPassword = !true || false = false

            seenApiChanges.add(change)
            return Violation.accept(member, "${rejection.getHumanExplanation()}. Reason for accepting this: <b>Upgraded property</b>")
        }

        def acceptanceJson = new AcceptedApiChange(
            change.type,
            change.member,
            '[ADD YOUR CUSTOM REASON HERE]',
            change.changes
        )

            """
        ) {
            assertHasErrors(
                "Field nonFinalField: Nullability breaking change.",
                "Field finalField: From non-nullable to nullable breaking change.",
                "Method com.example.Source.foo(): From non-null returning to null returning breaking change."
            )
            assertHasNoWarning()
            assertHasNoInformation()
        }
    }

    @Test