If an incoming request does not validate correctly then a `400` response will be sent.

## `GZipMiddleware` { #gzipmiddleware }

Handles GZip responses for any request that includes `"gzip"` in the `Accept-Encoding` header.

The middleware will handle both standard and streaming responses.

{* ../../docs_src/advanced_middleware/tutorial003_py310.py hl[2,6] *}

The following arguments are supported:

Some of the options you could use as a TLS Termination Proxy are:

* Traefik (that can also handle certificate renewals)
* Caddy (that can also handle certificate renewals)
* Nginx
* HAProxy

## Let's Encrypt { #lets-encrypt }

Before Let's Encrypt, these **HTTPS certificates** were sold by trusted third parties.

{* ../../docs_src/events/tutorial001_py310.py hl[8] *}

In this case, the `startup` event handler function will initialize the items "database" (just a `dict`) with some values.

You can add more than one event handler function.

And your application won't start receiving requests until all the `startup` event handlers have completed.

### `shutdown` event { #shutdown-event }

                    // Expected to catch exception silently
                }
            }
        };

        FwAssistantDirector assistantDirector = createMockAssistantDirector();

        // Should handle ClassNotFoundException gracefully
        customHook.hook(assistantDirector);

        // Verify no exception is thrown to the caller
        assertTrue(true);
    }

        // Mock Postbox - no need to mock, the framework will handle it

        // Register components
        ComponentUtil.register(searchEngineClient, "searchEngineClient");
        ComponentUtil.register(systemHelper, "systemHelper");
        ComponentUtil.setFessConfig(fessConfig);
        ComponentUtil.register(notificationHelper, "notificationHelper");
        // Postbox is handled by the framework

        // Execute

        } catch (Exception e) {
            // Expected due to missing dependencies in test environment
            assertTrue(true);
            return;
        }

        // Should handle case sensitivity properly
        assertNotNull(functionBuilders);
        assertEquals(0, functionBuilders.size()); // No data loaded
    }

    @Test
    public void test_load_emptyState() {
        try {

        try {
            dataIndexHelper.crawl("test-session-force-stop");
            assertTrue("Should exit quickly when force stopped", true);
        } catch (Exception e) {
            assertTrue("Force stop should handle exceptions quickly", true);
        }
    }

    @Test
    public void test_crawl_with_short_intervals() {
        try {
            // Test with minimal interval

Now let's go back a bit and understand what is all that.

The `password` "flow" is one of the ways ("flows") defined in OAuth2, to handle security and authentication.

OAuth2 was designed so that the backend or API could be independent of the server that authenticates the user.

But in this case, the same **FastAPI** application will handle the API and the authentication.

So, let's review it from that simplified point of view:

## Accessing the request body in an exception handler { #accessing-the-request-body-in-an-exception-handler }

/// tip

To solve this same problem, it's probably a lot easier to use the `body` in a custom handler for `RequestValidationError` ([Handling Errors](../tutorial/handling-errors.md#use-the-requestvalidationerror-body)).

# Advanced Security { #advanced-security }

## Additional Features { #additional-features }

There are some extra features to handle security apart from the ones covered in the [Tutorial - User Guide: Security](../../tutorial/security/index.md).

/// tip

The next sections are **not necessarily "advanced"**.

And it's possible that for your use case, the solution is in one of them.

///

## Read the Tutorial first { #read-the-tutorial-first }