"type": "string"
                    },
                    "type": {
                        "title": "Error Type",
                        "type": "string"
                    }
                }
            },
            "HTTPValidationError": {
                "title": "HTTPValidationError",
                "type": "object",
                "properties": {

// they are only defined to be used in this file alone.
type grantee struct {
	XMLNS       string `xml:"xmlns:xsi,attr"`
	XMLXSI      string `xml:"xsi:type,attr"`
	Type        string `xml:"Type"`
	ID          string `xml:"ID,omitempty"`
	DisplayName string `xml:"DisplayName,omitempty"`
	URI         string `xml:"URI,omitempty"`
}

type grant struct {
	Grantee    grantee `xml:"Grantee"`

     * @param key the decryption key
     * @param type the encryption type
     * @return the decrypted data
     * @throws GeneralSecurityException if decryption fails
     */
    public static byte[] decrypt(byte[] data, Key key, int type) throws GeneralSecurityException {
        Cipher cipher = null;
        byte[] decrypt = null;

        decrypt = switch (type) {

import org.codelibs.fess.crawler.helper.MimeTypeHelper;

/**
 * MimeTypeHelperImpl is a helper class that detects the MIME type of a given input stream or filename.
 * It uses the Apache Tika library to detect the MIME type.
 *
 * <p>
 * This class provides methods to:
 * </p>
 * <ul>
 *   <li>Detect the MIME type based on the input stream and filename.</li>
 *   <li>Normalize the filename to handle special characters.</li>

        return getMimeType(extension, "application/octet-stream");
    }

    /**
     * Returns the MIME type for the given file extension with a custom default.
     *
     * @param extension the file extension to look up (without the dot)
     * @param def the default MIME type to return if no mapping is found
     * @return the MIME type for the extension, or the specified default if not found

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

        // Test the second step (processing Type 2 and creating Type 3 message)
        when(mockAuth.getDomain()).thenReturn(domain);
        when(mockAuth.getUsername()).thenReturn(username);
        when(mockAuth.getPassword()).thenReturn(password);
        NtlmContext context = new NtlmContext(mockAuth, true);

        // State 1: Generate Type 1 message
        context.initSecContext(new byte[0], 0, 0);