}

    // These methods deal with construction intact Plugin object that look like they come from a standard
    // <plugin/> block in a Maven POM. We have to do some wiggling to pull the sources of information
    // together and this really shows the problem of constructing a sensible default configuration, but
    // it's all encapsulated here so it appears normalized to the POM builder.

But if you have custom headers that you want a client in a browser to be able to see, you need to add them to your CORS configurations ([CORS (Cross-Origin Resource Sharing)](cors.md)) using the parameter `expose_headers` documented in [Starlette's CORS docs](https://www.starlette.dev/middleware/#corsmiddleware).

///

/// note | Technical Details

# Learn { #learn }

Here are the introductory sections and the tutorials to learn **FastAPI**.

import org.junit.jupiter.api.TestInfo;
import org.opensearch.index.query.QueryBuilders;

import jakarta.annotation.Resource;

/**
 * @author shinsuke
 *
 */
public class OpenSearchUrlQueueServiceTest extends LastaDiTestCase {
    @Resource
    private OpenSearchUrlQueueService urlQueueService;

    @Resource
    private FesenClient fesenClient;

    private OpenSearchRunner runner;

    @Override

    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private RoleService roleService;
    @Resource
    private RolePager rolePager;

    // ===================================================================================

    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private BoostDocumentRuleService boostDocumentRuleService;
    @Resource
    private BoostDocPager boostDocPager;

    // ===================================================================================

    // Attribute
    // =========
    /** The search helper for performing search operations. */
    @Resource
    protected SearchHelper searchHelper;

    /** The search engine client for interacting with OpenSearch. */
    @Resource
    protected SearchEngineClient searchEngineClient;

    // ===================================================================================

import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.web.Execute;
import org.lastaflute.web.response.JsonResponse;
import org.opensearch.action.bulk.BulkResponse;

import jakarta.annotation.Resource;

/**
 * API action for admin document management.
 * Provides RESTful API endpoints for bulk document operations in the Fess search engine.

    }

    /**
     * Tests that the getter for the underlying pipe resource returns the correct instance.
     */
    @Test
    public void testGetPipe() {
        assertEquals(mockPipeResource, smbPipeHandle.getPipe(), "getPipe() should return the underlying pipe resource.");
    }

    /**
     * Tests that the getter for the input stream returns the correct stream.

Now that we have seen how to use `Path` and `Query`, let's see more advanced uses of request body declarations.

## Mix `Path`, `Query` and body parameters { #mix-path-query-and-body-parameters }

First, of course, you can mix `Path`, `Query` and request body parameter declarations freely and **FastAPI** will know what to do.

And you can also declare body parameters as optional, by setting the default to `None`: