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

    the output is different from (incorrect) previous versions. Note this
    breaking change only impacts `tf.image.extract_glimpse` and
    `tf.compat.v2.image.extract_glimpse` API endpoints. The behavior of
    `tf.compat.v1.image.extract_glimpse` does not change. The behavior of
    existing C++ kernel `ExtractGlimpse` does not change either, so saved models

     */
    int CAP_LARGE_READX = 0x4000;
    /**
     * Large write operations are supported capability.
     */
    int CAP_LARGE_WRITEX = 0x8000;
    /**
     * Extended security exchanges are supported capability.
     */
    int CAP_EXTENDED_SECURITY = 0x80000000;

    // file attribute encoding
    /**
     * File is marked read-only
     */
    int ATTR_READONLY = 0x01;
    /**

 * **Security** of the connection. This includes verification of the remote webserver with certificates and the privacy of data exchanged with strong ciphers.

        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 ")"
        }
        print "\n"
    }
}
}
print "\n\n"
}

    /**
     * Any attribute change in the watched directory or subtree causes a change notification wait operation to return.
     */
    int FILE_NOTIFY_CHANGE_ATTRIBUTES = 0x00000004;

    /**
     * Any file-size change in the watched directory or subtree causes a change notification wait operation to return.
     * The operating system detects a change in file size only when the file is written to the disk. For operating

    TFE_ContextOptions* options, const void* proto, size_t proto_len,
    TF_Status* status);

// Controls how to act when we try to run an operation on a given device but
// some input tensors are not on that device.
// LINT.IfChange
// Note: Keep in sync with internal copy of enum in eager/context.h.
typedef enum TFE_ContextDevicePlacementPolicy {
  // Running operations with input tensors on the wrong device will fail.
  TFE_DEVICE_PLACEMENT_EXPLICIT = 0,

## 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:
- [ ] Fixes a regression (If yes, please add `commit-id` or `PR #` here)

            while (handle.isActive()) {
                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