final SearchEngineClient esClient = ComponentUtil.getSearchEngineClient();
            final NodesStatsResponse response = esClient.admin().cluster().prepareNodesStats().all().execute().actionGet(10000L);
            final XContentBuilder builder = XContentFactory.jsonBuilder();
            builder.startObject();
            response.toXContent(builder, ToXContent.EMPTY_PARAMS);
            builder.endObject();
            builder.flush();

 */
package okhttp3

import kotlin.reflect.KClass
import okio.Timeout

open class FailingCall : Call {
  override fun request(): Request = error("unexpected")

  override fun execute(): Response = error("unexpected")

  override fun enqueue(responseCallback: Callback): Unit = error("unexpected")

  override fun cancel(): Unit = error("unexpected")

  override fun isExecuted(): Boolean = error("unexpected")

	// ErrIncorrectSequence is returned when an out-of-sequence item is received.
	ErrIncorrectSequence = errors.New("out-of-sequence item received")
)

// ErrResponse is a remote error response.
type ErrResponse struct {
	msg string
}

func (e ErrResponse) Error() string {
	return fmt.Sprintf("remote: %s", e.msg)

El valor del parámetro de path `item_id` se pasará a tu función como el argumento `item_id`.

Así que, si ejecutas este ejemplo y vas a [http://127.0.0.1:8000/items/foo](http://127.0.0.1:8000/items/foo), verás un response de:

```JSON
{"item_id":"foo"}
```

## Parámetros de path con tipos { #path-parameters-with-types }

Puedes declarar el tipo de un parámetro de path en la función, usando anotaciones de tipos estándar de Python:

The value of the path parameter `item_id` will be passed to your function as the argument `item_id`.

So, if you run this example and go to [http://127.0.0.1:8000/items/foo](http://127.0.0.1:8000/items/foo), you will see a response of:

```JSON
{"item_id":"foo"}
```

## Path parameters with types { #path-parameters-with-types }

You can declare the type of a path parameter in the function, using standard Python type annotations:

            packet.readTrailerWireFormat(mockInputStream, buffer, 0);
        });
        assertTrue(thrown.getMessage().contains("unexpected EOF reading netbios retarget session response"));
    }

   readTimeoutMillis, retryOnConnectionFailure, socketFactory, sslSocketFactory, writeTimeoutMillis
 * **PushPromise**: headers, method, path, response
 * **Request**: body, cacheControl, headers, method, url
 * **Response**: body, cacheControl, cacheResponse, code, handshake, headers, message,
   networkResponse, priorResponse, protocol, receivedResponseAtMillis, request, sentRequestAtMillis

        HandleGuid guid = new HandleGuid();

        // Create handle info with empty file ID (will be populated after successful create response)
        HandleInfo info = new HandleInfo(path, guid, new byte[16], type, timeout, leaseKey);

        lock.writeLock().lock();
        try {
            handles.put(path, info);

        setupMockContext();
        Smb2IoctlRequest request = new Smb2IoctlRequest(mockConfig, TEST_CONTROL_CODE, TEST_FILE_ID, TEST_OUTPUT_BUFFER);

        Smb2IoctlResponse response = request.createResponse(mockContext, request);

        assertNotNull(response);
        verify(mockContext).getConfig();
    }

    @Test
    @DisplayName("Test setFlags method")
    void testSetFlags() {
        setupMockConfig();

{* ../../docs_src/stream_data/tutorial001_py310.py ln[44:47] hl[47] *}

## A Custom `PNGStreamingResponse` { #a-custom-pngstreamingresponse }

In the examples above, the data bytes were streamed, but the response didn't have a `Content-Type` header, so the client didn't know what type of data it was receiving.

You can create a custom sub-class of `StreamingResponse` that sets the `Content-Type` header to the type of data you're streaming.