return systemHelper.getRedirectResponseToRoot(newHtmlResponseAsRedirect("/"));
    }

    /**
     * Processes the given path through the virtual host helper to handle
     * virtual host configurations and path modifications.
     *
     * @param path the HTML path to process
     * @return the processed path with virtual host handling applied
     */
    protected HtmlNext virtualHost(final HtmlNext path) {

import org.codelibs.fess.util.JobProcess;

import jakarta.annotation.PreDestroy;

/**
 * Helper class for managing system processes in Fess.
 * This class provides functionality to start, stop, and manage external processes
 * such as crawler processes, with proper resource cleanup and lifecycle management.
 */
public class ProcessHelper {
    /** Logger instance for this class */

* Restarts
* **Replication (the number of processes running)**
* Memory
* Previous steps before starting

Up to this point, with all the tutorials in the docs, you have probably been running a **server program**, for example, using the `fastapi` command, that runs Uvicorn, running a **single process**.

        }
        return urlSet;
    }

    /**
     * Processes the response data from a crawled URL, including failure handling.
     * This method extends the base response processing to handle Fess-specific failure
     * URL tracking when certain HTTP status codes are encountered.
     *
     * @param urlQueue the URL queue item that was processed
     * @param responseData the response data from the crawl operation
     */

### Containers with Multiple Processes and Special Cases { #containers-with-multiple-processes-and-special-cases }

Of course, there are **special cases** where you could want to have **a container** with several **Uvicorn worker processes** inside.

In those cases, you can use the `--workers` command line option to set the number of workers that you want to run:

A "middleware" is a function that works with every **request** before it is processed by any specific *path operation*. And also with every **response** before returning it.

* It takes each **request** that comes to your application.
* It can then do something to that **request** or run any needed code.
* Then it passes the **request** to be processed by the rest of the application (by some *path operation*).

    public void test_execute_success() {
        String result = updateLabelJob.execute();
        assertNotNull(result);
        assertTrue(result.contains("3 docs")); // 3 documents processed
        assertFalse(result.contains("exception"));
    }

    // Test execute() method with query builder
    public void test_execute_withQueryBuilder() {

import org.opensearch.search.aggregations.bucket.terms.Terms;

import com.google.common.io.BaseEncoding;

/**
 * Response object for faceted search results containing query counts and field facets.
 * This class processes OpenSearch aggregations to provide structured facet information
 * for search result filtering and navigation.
 */
public class FacetResponse {
    /**

    /**
     * Current status of the crawler.
     */
    protected volatile CrawlerStatus status = CrawlerStatus.INITIALIZING;

    /**
     * Filter for URLs to control which URLs are processed.
     */
    protected UrlFilter urlFilter;

    /**
     * Manager for crawling rules and configurations.
     */
    protected RuleManager ruleManager;

    /**

 * to process template strings with parameter substitution.
 */
public interface ScriptEngine {

    /**
     * Evaluates a template string with the provided parameter map.
     * The template is processed using the script engine's templating mechanism,
     * with parameters from the paramMap substituted into the template.
     *
     * @param template the template string to evaluate