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();

    public val shutdownOutput: Boolean = false,
  ) : SocketEffect

  /**
   * On HTTP/2, send a [GOAWAY frame](https://tools.ietf.org/html/rfc7540#section-6.8) immediately
   * after the response and will close the connection when the client's socket is exhausted.
   *
   * On HTTP/1 this closes the socket.
   */
  public object ShutdownConnection : SocketEffect

  /**

        if (in.read(buffer, bufferIndex, length) != length) {
            throw new IOException("unexpected EOF reading netbios retarget session response");
        }
        final int addr = readInt4(buffer, bufferIndex);
        bufferIndex += 4;
        retargetAddress = new NbtAddress(null, addr, false, NbtAddress.B_NODE);

{* ../../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.

        JSON,
        /** GSA request type. */
        GSA,
        /** Suggest request type. */
        SUGGEST;
    }

    /**
     * Returns the response fields.
     *
     * @return The response fields.
     */
    public String[] getResponseFields() {
        return ComponentUtil.getQueryFieldConfig().getResponseFields();
    }

     *      jcifs.internal.smb1.com.SmbComNTCreateAndXResponse)
     */
    @Override
    protected void customizeCreate(final SmbComNTCreateAndX request, final SmbComNTCreateAndXResponse response) {
        request.addFlags0(0x16);
        response.setExtended(true);
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.smb.SmbFile#getType()
     */
    @Override

	if err != nil {
		if xnet.IsNetworkOrHostDown(err, true) {
			return false, errNotConnected
		}
		return false, err
	}
	xhttp.DrainBody(resp.Body)
	// No network failure i.e response from the target means its up
	return true, nil
}

// Stat - returns lambda webhook target statistics such as
// current calls in progress, successfully completed functions
// failed functions.

        if (in.read(buffer, bufferIndex, this.length) != this.length) {
            throw new IOException("unexpected EOF reading netbios retarget session response");
        }
        final int addr = readInt4(buffer, bufferIndex);
        bufferIndex += 4;
        new NbtAddress(null, addr, false, NbtAddress.B_NODE);
        readInt2(buffer, bufferIndex);