// There is no need to use an existing bucket and valid input for creating the request
	// since the `objectLayer==nil`  check is performed before any other checks inside the handlers.
	// The only aim is to generate an HTTP request in a way that the relevant/registered end point is evoked/called.
	nilBucket := "dummy-bucket"

jiuker <******@****.***> 1754621164 +0800

        lock.readLock().lock();
        try {
            return handles.get(path);
        } finally {
            lock.readLock().unlock();
        }
    }

    /**
     * Get the number of active handles
     * @return the number of handles
     */
    public int getHandleCount() {
        return handles.size();
    }

    private void periodicMaintenance() {
        if (shutdown) {

Klaus Post <******@****.***> 1739895955 -0800

Klaus Post <******@****.***> 1759093161 +0200

Klaus Post <******@****.***> 1759093161 +0200

        factoryField.set(null, null);

        // Clear the protocol handlers cache
        Field handlersField = Handler.class.getDeclaredField("PROTOCOL_HANDLERS");
        handlersField.setAccessible(true);
        @SuppressWarnings("unchecked")
        Map<String, URLStreamHandler> handlers = (Map<String, URLStreamHandler>) handlersField.get(null);
        handlers.clear();
    }

    /**

///

## Override the default exception handlers { #override-the-default-exception-handlers }

**FastAPI** has some default exception handlers.

These handlers are in charge of returning the default JSON responses when you `raise` an `HTTPException` and when the request has invalid data.

You can override these exception handlers with your own.

* `"function"`: start the dependency before the *path operation function* that handles the request, end the dependency after the *path operation function* ends, but **before** the response is sent back to the client. So, the dependency function will be executed **around** the *path operation **function***.

and other connections will be blocked while the large payload is being sent.

## Handlers & Routes

Handlers have a predefined Handler ID.
In addition, there can be several *static* subroutes used to differentiate between different handlers of the same ID.
A subroute on a client must match a subroute on the server. So routes cannot be used for dynamic routing, unlike HTTP.