if (newBufferSize > MAX_BUF_SIZE) {
                        throw new IORuntimeException(new IOException("Content too large: exceeds maximum buffer size of " + MAX_BUF_SIZE + " bytes. Use streaming APIs for large content."));
                    }
                    final char[] newBuf = new char[newBufferSize];
                    System.arraycopy(buf, 0, newBuf, 0, bufferSize);

 * </p>
 * <ul>
 *   <li>Starting and finishing threads</li>
 *   <li>Starting and cleaning up crawling</li>
 *   <li>Handling unsupported URLs</li>
 *   <li>Checking last modified dates</li>
 *   <li>Getting content</li>
 *   <li>Handling redirects</li>
 *   <li>Processing responses</li>
 *   <li>Handling exceptions during crawling and child URL processing</li>
 *   <li>Handling cases where no URL is in the queue</li>

direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a

 *
 * <p>Duplicate host configurations allow administrators to define hostname patterns
 * that should be treated as equivalent during crawling. This helps avoid indexing
 * duplicate content from the same logical site that may be accessible via different
 * hostnames (e.g., www.example.com and example.com).</p>
 */
public class DuplicateHostService extends FessAppService {

    /**

/**
 * API action for admin duplicate host management.
 * Provides RESTful API endpoints for managing duplicate host settings in the Fess search engine.
 * Duplicate host settings help prevent indexing the same content from multiple similar URLs.
 *
 */
public class ApiAdminDuplicatehostAction extends FessApiAdminAction {

    private static final Logger logger = LogManager.getLogger(ApiAdminDuplicatehostAction.class);

        // Buffer length is based on maximum_length/2 from the encoded data
        assertEquals(translatedName.name.maximum_length / 2, decodedName.name.buffer.length);
        // Verify the actual string content
        for (int i = 0; i < translatedName.name.buffer.length; i++) {
            assertEquals(translatedName.name.buffer[i], decodedName.name.buffer[i]);
        }

    <example>${fe:replace(input, regex, replacement)}</example>
  </function>

  <function>
    <description>Format a content as code.</description>
    <name>formatCode</name>
    <function-class>org.codelibs.fess.taglib.FessFunctions</function-class>

        assertTrue(passwordValue instanceof char[], "Password should be stored as char[]");
        assertArrayEquals("password123".toCharArray(), (char[]) passwordValue, "Password content should match");
    }

    @Test
    @DisplayName("Test secure password wipe")
    void testSecureWipePassword() throws Exception {
        String testPassword = "testPassword123";

    }

    /**
     * Processes search preferences specifically for JSON API requests.
     * This method determines the preference value based on configuration and query content.
     *
     * @param req the HTTP servlet request
     * @param query the search query string
     * @return the preference value for JSON search requests, or null if not applicable
     */

        goodCertificate.certificate,
      )
    server.useHttps(socketFactory)
    server.enqueue(
      MockResponse
        .Builder()
        .body("abc")
        .addHeader("Content-Type: text/plain")
        .build(),
    )

    // Make a request from client to server. It should succeed certificate checks (unfortunately the
    // rogue CA is trusted) but it should fail certificate pinning.