Interceptors can be chained. Suppose you have both a compressing interceptor and a checksumming interceptor: you'll need to decide whether data is compressed and then checksummed, or checksummed and then compressed. OkHttp uses lists to track interceptors, and interceptors are called in order.

 * This class provides methods to retrieve paths for configuration files, templates, dictionaries,
 * thumbnails, plugins, and other resources required by the Fess search engine.
 * It supports both regular deployment and Docker container environments.
 *
 */
public class ResourceUtil {
    /** Environment variable name for overriding the configuration path */

        buffer = createValidResponseBuffer(0, 0x2, 0, 0);
        response.readBytesWireFormat(buffer, 0);
        assertTrue(response.isShareDfs());

        // Test with both DFS flags
        response = new Smb2TreeConnectResponse(mockConfig);
        buffer = createValidResponseBuffer(0, 0x3, 0, 0);
        response.readBytesWireFormat(buffer, 0);
        assertTrue(response.isShareDfs());

// For objects in "Compliance" mode, retention date cannot be shortened, and mode cannot be altered.
// For objects with legal hold header set, the s3:PutObjectLegalHold permission is expected to be set
// Both legal hold and retention can be applied independently on an object

     *
     * RFC 2388 is rather vague about how one should escape special characters in form-data
     * parameters, and as it turns out Firefox and Chrome actually do rather different things, and
     * both say in their comments that they're not really sure what the right approach is. We go
     * with Chrome's behavior (which also experimentally seems to match what IE does), but if you

    if (!disjoint(allPresentFeatures, allAbsentFeatures)) {
      throw new ConflictingRequirementsException(
          "Annotation explicitly or "
              + "implicitly requires one or more features to be both present "
              + "and absent.",
          intersection(allPresentFeatures, allAbsentFeatures),
          testerAnnotation);
    }
    return new TesterRequirements(allPresentFeatures, allAbsentFeatures);
  }

    void testMultipleReads() throws SMBProtocolDecodingException {
        // Given
        byte[] buffer1 = new byte[256];
        byte[] buffer2 = new byte[256];

        // Prepare both buffers with valid structure
        SMBUtil.writeInt2(4, buffer1, 0);
        SMBUtil.writeInt2(0, buffer1, 2);
        SMBUtil.writeInt2(4, buffer2, 10);
        SMBUtil.writeInt2(0, buffer2, 12);

        // When

        }
    }

    @Nested
    @DisplayName("Chain Operation Tests")
    class ChainOperationTests {

        @Test
        @DisplayName("allowChain should check configuration for both requests")
        void testAllowChain() {
            TestServerMessageBlock2Request nextRequest = new TestServerMessageBlock2Request(mockConfig);

 * invoke methods, they invoke methods on the {@code ForwardingMap}.
 *
 * <p>Each of the {@code standard} methods, where appropriate, use {@link Objects#equals} to test
 * equality for both keys and values. This may not be the desired behavior for map implementations
 * that use non-standard notions of key equality, such as a {@code SortedMap} whose comparator is
 * not consistent with {@code equals}.
 *

 *
 * <p><a id="bitEquals"></a>This class compares primitive {@code double} values in methods such as
 * {@link #compareAndSet} by comparing their bitwise representation using {@link
 * Double#doubleToRawLongBits}, which differs from both the primitive double {@code ==} operator and
 * from {@link Double#equals}, as if implemented by:
 *
 * {@snippet :
 * static boolean bitEquals(double x, double y) {
 *   long xBits = Double.doubleToRawLongBits(x);