// Standard lease V2 size: LeaseKey(16) + LeaseState(4) + Flags(4) + reserved fields
        return 32;
    }

    @Override
    public int size() {
        // Context header: 16 bytes
        // Name: 4 bytes ("DLse")
        // Padding: 4 bytes (to align data to 8-byte boundary)
        // Standard lease data: 32 bytes

    
    public DurableHandleRequest() {
        super(NAME);
        this.reserved = 0;
    }
    
    @Override
    public void encode(byte[] buffer, int offset) {
        // Context header
        int nameLen = getName().length();
        writeInt4(buffer, offset, 16);  // Next
        writeInt2(buffer, offset + 4, nameLen);  // NameOffset
        writeInt2(buffer, offset + 6, nameLen);  // NameLength

    private static final String CRAWLER_WEB_PREFIX = "crawler.web.";

    private static final String CRAWLER_WEB_HEADER_PREFIX = CRAWLER_WEB_PREFIX + "header.";

    private static final String CRAWLER_WEB_AUTH = CRAWLER_WEB_PREFIX + "auth";

    private static final String CRAWLER_USERAGENT = "crawler.useragent";

import org.mockito.quality.Strictness;

import jcifs.Configuration;

/**
 * Unit tests for {@link SmbComQueryInformation}.  The class is very small and
 * mainly focuses on serialising a command header that contains a file name.
 * <p>
 * Because most of the logic lives in {@link jcifs.internal.smb1.ServerMessageBlock}
 * the tests create a mock {@link Configuration} and instantiate SmbComQueryInformation

     * Some fields specify the offset from the beginning of the header. This
     * field should be used for calculating that. This would likely be zero
     * but an implemantation that encorporates the transport header(for
     * efficiency) might use a different initial bufferIndex. For example,
     * to eliminate copying data when writing NbtSession data one might
     * manage that 4 byte header specifically and therefore the initial

        byte[] encoded = AvPairs.encode(pairs);

        assertNotNull(encoded, "Encoded data should not be null");

        int expectedLength = 4 + 4 + // AvFlags header + data
                4 + 8 + // AvTimestamp header + data
                4 + 4 + // AvTargetName header + data
                4; // EOL
        assertEquals(expectedLength, encoded.length, "Encoded length should match expected");

        // Verify EOL at the end

          + ")") : "(cache)";
      int responseCode = response.code();

      System.out.printf("%03d: %s %s%n", responseCode, url, responseSource);

      String contentType = response.header("Content-Type");
      if (responseCode != 200 || contentType == null) {
        return;
      }

      MediaType mediaType = MediaType.parse(contentType);

                                     readRegion.getAddress(),
                                     readRegion.getSize());
            
            // Send request header via RDMA send
            sendWithRdmaSendReceive(request);
            
            // Wait for server to write data directly to our buffer via RDMA

 *        * body ([responseBodyStart], [responseBodyEnd])
 *
 * This nesting is typical but not strict. For example, when calls use "Expect: continue" the
 * request body start and end events occur within the response header events. Similarly,
 * [duplex calls][RequestBody.isDuplex] interleave the request and response bodies.
 *
 * Since connections may be reused, the proxy selection, DNS, and connect events may not be present

labels.roletype_title_details=Role
labels.roletype_name=Name
labels.roletype_value=Value
labels.reqheader_configuration=Request Header
labels.reqheader_list_name=Name
labels.reqheader_list_web_crawling_config=Config Name
labels.reqheader_create_web_config=Create New Web Config
labels.reqheader_title_details=Request Header
labels.reqheader_name=Name
labels.reqheader_value=Value
labels.reqheader_web_crawling_config=Web Config