* </p>
     * <ul>
     *   <li>Main resources with {@code targetPath="META-INF"} are copied to {@code target/classes/META-INF}</li>
     *   <li>Test resources with {@code targetPath="test-data"} are copied to {@code target/test-classes/test-data}</li>
     *   <li>Resources without an explicit {@code targetPath} are copied to the root of the output directory</li>
     * </ul>
     * <p>
     * <strong>Maven 3 Compatibility:</strong>

	if err != nil {
		writeErrorResponseJSON(ctx, w, toAdminAPIErr(ctx, err), r.URL)
		return
	}

	data, err := json.Marshal(chEntries)
	if err != nil {
		writeErrorResponseJSON(ctx, w, toAdminAPIErr(ctx, err), r.URL)
		return
	}

	password := cred.SecretKey
	econfigData, err := madmin.EncryptData(password, data)
	if err != nil {
		writeErrorResponseJSON(ctx, w, toAdminAPIErr(ctx, err), r.URL)
		return
	}

///

## 資料 <dfn title="也稱為：序列化、解析、封送">轉換</dfn> { #data-conversion }

如果你執行這個範例並在瀏覽器開啟 [http://127.0.0.1:8000/items/3](http://127.0.0.1:8000/items/3)，你會看到這樣的回應：

```JSON
{"item_id":3}
```

/// check

注意你的函式接收（並回傳）的值是 `3`，也就是 Python 的 `int`，而不是字串 `"3"`。

因此，有了這個型別宣告，**FastAPI** 會自動為你處理請求的 <dfn title="將 HTTP 請求中的字串轉換為 Python 資料">「解析」</dfn>。

///

## 資料驗證 { #data-validation }

        lenient().when(mockHost.getHostName()).thenReturn("TEST_HOSTNAME");

        return mockCtx;
    }

    @Test
    @DisplayName("Should create Type 3 message with authentication data")
    void testType3MessageCreation() throws Exception {
        // Given
        Type2Message type2 = createMockType2Message();
        String password = "testpassword";
        String domain = "TESTDOMAIN";

sealed class SocketMode

object Channel : SocketMode() {
  override fun toString(): String = "Channel"
}

object Standard : SocketMode() {
  override fun toString(): String = "Standard"
}

data class TlsInstance(
  val provider: Provider,
  val protocol: Protocol,
  val tlsVersion: TlsVersion,
  val socketMode: SocketMode,
  val tlsExtensionMode: TlsExtensionMode,
) : SocketMode() {

import jcifs.internal.util.SMBUtil;

/**
 * SMB 3.1.1 Compression Capabilities negotiate context.
 *
 * This context is used during SMB2 negotiation to negotiate compression
 * algorithms for SMB3 data compression support.
 */
public class CompressionNegotiateContext implements NegotiateContextRequest, NegotiateContextResponse {

    private static final Logger log = LoggerFactory.getLogger(CompressionNegotiateContext.class);

    /**
     * Processes an HTTP method request and returns the response data.
     * This method handles the complete HTTP request lifecycle including content processing,
     * redirect handling, and error management.
     *
     * @param url The URL being accessed
     * @param httpRequest The HTTP request to process
     * @return The response data containing the retrieved information
     */

            op.rangeSize(fessConfig.getPagingPageRangeSizeAsInteger());
        }).createPageNumberList());

        return webConfigList;
    }

    /**
     * Deletes a web configuration and all its related data.
     * This includes removing associated web authentications and request headers.
     *
     * @param webConfig The web configuration to delete
     */
    public void delete(final WebConfig webConfig) {

 * bookkeeping easier for the caller: releasing the allocation as soon as the terminal stream has
 * been found. But only complete the stream once its data stream has been exhausted.
 */
interface Connection {
  /** Returns the route used by this connection. */
  fun route(): Route

  /**
   * Returns the socket that this connection is using. Returns an

   */
  @Override
  Set<V> values();

  /**
   * Returns the inverse view of this bimap, which maps each of this bimap's values to its
   * associated key. The two bimaps are backed by the same data; any changes to one will appear in
   * the other.
   *
   * <p><b>Note:</b> There is no guaranteed correspondence between the iteration order of a bimap
   * and that of its inverse.
   *