It uses a single two-way connection to send and receive messages between servers.

It includes built in muxing of concurrent requests as well as congestion handling for streams.

Requests can be "Single Payload" or "Streamed".

Use the MinIO Grid for:

* Small, frequent requests with low latency requirements.
* Long-running requests with small/medium payloads.

Do *not* use the MinIO Grid for:

* Large payloads.

## Requests ohne Content-Type erlauben { #allowing-requests-without-content-type }

Wenn Sie Clients unterstützen müssen, die keinen `Content-Type`-Header senden, können Sie die strikte Prüfung deaktivieren, indem Sie `strict_content_type=False` setzen:

{* ../../docs_src/strict_content_type/tutorial001_py310.py hl[4] *}

```

> NOTE: You can configure the `scopes` parameter to restrict the OpenID scopes requested by minio to the IdP, for example, `"openid,policy_role_attribute"`, being `policy_role_attribute` a client_scope / client_mapper that maps a role attribute called policy to a `policy` claim returned by Keycloak

     *
     * @return maxmimum number of elements to request in a list request
     */
    int getListCount();

    /**
     *
     * Property {@code jcifs.smb.client.listSize} (int, default 65435)
     *
     * @return maximum data size for list/info requests (known overhead is subtracted)
     */
    int getListSize();

    /**
     *
     *

The middleware responds to two particular types of HTTP request...

### CORS preflight requests { #cors-preflight-requests }

These are any `OPTIONS` request with `Origin` and `Access-Control-Request-Method` headers.

In this case the middleware will intercept the incoming request and respond with appropriate CORS headers, and either a `200` or `400` response for informational purposes.

### Simple requests { #simple-requests }

## Allowing Requests Without Content-Type { #allowing-requests-without-content-type }

If you need to support clients that don't send a `Content-Type` header, you can disable strict checking by setting `strict_content_type=False`:

{* ../../docs_src/strict_content_type/tutorial001_py310.py hl[4] *}

     */
    int FLAGS_PATH_NAMES_CASELESS = 0x08;
    /**
     * Path names are canonicalized flag.
     */
    int FLAGS_PATH_NAMES_CANONICALIZED = 0x10;
    /**
     * Opportunistic lock requested or granted flag.
     */
    int FLAGS_OPLOCK_REQUESTED_OR_GRANTED = 0x20;
    /**
     * Notify client of any action which modified the file flag.
     */
    int FLAGS_NOTIFY_OF_MODIFY_ACTION = 0x40;
    /**

            CreateContextRequest request = mock(CreateContextRequest.class);
            when(request.getName()).thenReturn(expectedName);

            byte[] actualName = request.getName();
            assertArrayEquals(expectedName, actualName);
            verify(request, times(1)).getName();
        }

        @Test

                  "mode": "fixed"
                }
              }
            ]
          },
          {
            "matcher": {
              "id": "byName",
              "options": "Replication Requests"
            },
            "properties": [
              {
                "id": "color",
                "value": {
                  "fixedColor": "light-green",
                  "mode": "fixed"

También defines de alguna manera en qué **momentos** tu aplicación enviará esas requests o eventos.

Y **tus usuarios** definen de alguna manera (por ejemplo en un panel web en algún lugar) el **URL** donde tu aplicación debería enviar esas requests.