Metrics with a `/bucket` component in the path return results for each specified bucket in the deployment. These endpoints **require** providing a list of buckets as a `bucket` query parameter.  The endpoint then returns only metrics for the given buckets, with the bucket name in a `bucket` label.

For example, to query API metrics for buckets `test1` and `test2`, make a scrape request to `/minio/metrics/v3/api/bucket?buckets=test1,test2`. 

### List Available Metrics

    private int fileAttributes = 0x0000;
    private long lastWriteTime = 0L;
    private final long serverTimeZoneOffset;
    private int fileSize = 0;

    /**
     * Constructs a query information response.
     *
     * @param config the configuration
     * @param serverTimeZoneOffset the server time zone offset
     */

 * They don't specify whether a specific proxy server should be used or how to authenticate with that proxy server.

They're also concrete: each URL identifies a specific path (like `/square/okhttp`) and query (like `?q=sharks&lang=en`). Each webserver hosts many URLs.

### [Addresses](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-address/)

                    while (timeout > 0) {
                        response.wait(timeout);

                        /* JetDirect printer can respond to regular broadcast query
                         * with node status so we need to check to make sure that
                         * the record type matches the question type and if not,
                         * loop around and try again.

 */
package jcifs.internal;

import jcifs.internal.fscc.FileSystemInformation;

/**
 * Interface for file system allocation information providing capacity and free space details.
 * Used in SMB protocol operations to query disk space information from remote SMB shares.
 *
 * @author mbechler
 */
public interface AllocInfo extends FileSystemInformation {

    /**
     * Gets the total capacity of the allocation.
     *

## Importe `File` e `Form`

{* ../../docs_src/request_forms_and_files/tutorial001.py hl[1] *}

## Defina parâmetros de `File` e `Form`

Crie parâmetros de arquivo e formulário da mesma forma que você faria para `Body` ou `Query`:

{* ../../docs_src/request_forms_and_files/tutorial001.py hl[8] *}

Os arquivos e campos de formulário serão carregados como dados de formulário e você receberá os arquivos e campos de formulário.

import org.codelibs.fess.opensearch.config.exentity.CrawlingInfo;
import org.codelibs.fess.opensearch.config.exentity.CrawlingInfoParam;
import org.codelibs.fess.util.ComponentUtil;
import org.opensearch.index.query.QueryBuilders;
import org.opensearch.search.aggregations.AggregationBuilders;
import org.opensearch.search.aggregations.BucketOrder;
import org.opensearch.search.aggregations.bucket.terms.Terms;

/** File generated by Grunt -- do not modify
 *  JQUERY-FORM-VALIDATOR
 *
 *  @version 2.3.77
 *  @website http://formvalidator.net/
 *  @author Victor Jonsson, http://victorjonsson.se
 *  @license MIT
 */

    private final int informationLevel;

    /**
     * Constructs a Trans2QueryFSInformation request.
     *
     * @param config the SMB configuration
     * @param informationLevel the file system information level to query
     */
    public Trans2QueryFSInformation(final Configuration config, final int informationLevel) {
        super(config, SMB_COM_TRANSACTION2, TRANS2_QUERY_FS_INFORMATION);
        this.informationLevel = informationLevel;

例えば、`pip install python-multipart`のように。

///

## `File`と`Form`のインポート

{* ../../docs_src/request_forms_and_files/tutorial001.py hl[1] *}

## `File`と`Form`のパラメータの定義

ファイルやフォームのパラメータは`Body`や`Query`の場合と同じように作成します:

{* ../../docs_src/request_forms_and_files/tutorial001.py hl[8] *}

ファイルとフォームフィールドがフォームデータとしてアップロードされ、ファイルとフォームフィールドを受け取ります。

また、いくつかのファイルを`bytes`として、いくつかのファイルを`UploadFile`として宣言することができます。