label: "Proposal"
      description: "What is the proposed change? Who does this proposal help, and why? Please describe as precisely as possible the change to the language."
    validations:
      required: true

  - type: textarea
    id: language-spec-changes
    attributes:
      label: "Language Spec Changes"
      description: "What would change in the language spec?"
    validations:
      required: false

# Response - Change Status Code { #response-change-status-code }

You probably read before that you can set a default [Response Status Code](../tutorial/response-status-code.md){.internal-link target=_blank}.

But in some cases you need to return a different status code than the default.

## Use case { #use-case }

For example, imagine that you want to return an HTTP status code of "OK" `200` by default.

Sebastián Ramírez <******@****.***> 1735580804 +0000

Sebastián Ramírez <******@****.***> 1731896744 +0100

Sebastián Ramírez <******@****.***> 1731896744 +0100

Sebastián Ramírez <******@****.***> 1731896744 +0100

Sebastián Ramírez <******@****.***> 1731896744 +0100

Naves <******@****.***> 1750072270 +0300

## 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:

    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