// Server sent a 100-continue even though we did not request one. Try again to read the
      // actual response status.
      code == 100 -> true

      // Handle Processing (102) & Early Hints (103) and any new codes without failing
      // 100 and 101 are the exceptions with different meanings
      // But Early Hints not currently exposed
      code in (102 until 200) -> true

      else -> false
    }

 * were inserted, not how those bytes were chunked into discrete put() operations. For example, the
 * following three expressions all generate colliding hash codes:
 *
 * {@snippet :
 * newHasher().putByte(b1).putByte(b2).putByte(b3).hash()
 * newHasher().putByte(b1).putBytes(new byte[] { b2, b3 }).hash()
 * newHasher().putBytes(new byte[] { b1, b2, b3 }).hash()
 * }
 *

        return fessConfig.isCrawlerDocumentDuplicateTermRemoved();
    }

    /**
     * Gets the array of space character codes from configuration.
     *
     * @return array of character codes to be treated as spaces
     */
    protected int[] getSpaceChars() {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

	} `xml:"Error"`
	RequestID string `xml:"RequestId"`
}

// STSErrorCode type of error status.
type STSErrorCode int

//go:generate stringer -type=STSErrorCode -trimprefix=Err $GOFILE

// Error codes, non exhaustive list - http://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithSAML.html
const (
	ErrSTSNone STSErrorCode = iota
	ErrSTSAccessDenied
	ErrSTSMissingParameter
	ErrSTSInvalidParameterValue

    /**
     * Returns the type of this SID indicating the state or type of account.
     * <p>
     * SID types are described in the following table.
     * <table>
     * <caption>Type codes</caption>
     * <tr>
     * <th>Type</th>
     * <th>Name</th>
     * </tr>
     * <tr>
     * <td>SID_TYPE_USE_NONE</td>
     * <td>0</td>
     * </tr>
     * <tr>
     * <td>SID_TYPE_USER</td>

<img src="/img/tutorial/response-status-code/image01.png">

/// note | 注意

有些回應碼（見下一節）表示回應不包含本文（body）。

FastAPI 知道這點，並會產生聲明「無回應本文」的 OpenAPI 文件。

///

## 關於 HTTP 狀態碼 { #about-http-status-codes }

/// note | 注意

如果你已經知道什麼是 HTTP 狀態碼，可以直接跳到下一節。

///

在 HTTP 中，你會在回應的一部分傳回 3 位數的狀態碼。

這些狀態碼有對應的名稱以便辨識，但重點是數字本身。

簡而言之：

* `100 - 199` 表示「資訊」。你很少會直接使用它們。這些狀態碼的回應不可包含本文。

	ErrTooManyRequests
	ErrInvalidRequest
	ErrTransitionStorageClassNotFoundError
	// MinIO storage class error codes
	ErrInvalidStorageClass
	ErrBackendDown
	// Add new extended error codes here.
	// Please open a https://github.com/minio/minio/issues before adding
	// new error codes here.

	ErrMalformedJSON
	ErrAdminNoSuchUser
	ErrAdminNoSuchUserLDAPWarn
	ErrAdminLDAPExpectedLoginName

        assertEquals(metadataHashCode, SsoResponseType.METADATA.hashCode());
        assertEquals(logoutHashCode, SsoResponseType.LOGOUT.hashCode());

        // Different enum constants should have different hash codes (usually)
        assertNotSame(metadataHashCode, logoutHashCode);
    }

    @Test
    public void test_compareTo() {
        // Test compareTo method for enum constants

        super.tearDown(testInfo);
    }

    // Test basic initialization
    @Test
    public void test_hookInitialization() {
        assertNotNull(apiFailureHook);
    }

    // Test API result status codes
    @Test
    public void test_apiResultStatusCodes() {
        // Test OK status
        ApiResult okResult = new ApiResult.ApiResponse().status(Status.OK).result();
        assertNotNull(okResult);

        assertTrue(result1.startsWith("FessUserTimeZoneProcessProvider:{"));
        assertTrue(result2.startsWith("FessUserTimeZoneProcessProvider:{"));

        // But different hash codes
        assertFalse(result1.equals(result2));
    }

    // Test static field initialization
    @Test
    public void test_centralTimeZone_initialization() {